Joined: 21 May 2009 Posts: 139 Location: United States
EXEC PGM=SORT,PARM='RC16=NORC16' gives the following-
Code:
WER131I PARM FIELD ERROR - RC16=NOR
WER276B SYSDIAG= 3302559, 4958040, 4958040, 4731549
WER164B 7,908K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 2,339,720 BYTES USED
WER146B 32K BYTES OF EMERGENCY SPACE ALLOCATED
WER108I SORTIN : RECFM=FB ; LRECL= 400; BLKSIZE= 27600
WER257I INREC RECORD LENGTH = 406
WER238I POTENTIALLY INEFFICIENT USE OF INREC
WER110I SORTOF01 : RECFM=FB ; LRECL= 400; BLKSIZE= 27600
WER410B 5,856K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,
WER410B 0 BYTES RESERVE REQUESTED, 2,192,264 BYTES USED
WER405I SORTOF01 : DATA RECORDS OUT 0; TOTAL RECORDS OUT
WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000
WER461A SORTOUT/OUTFIL DATA SET CONTAINS NO DATA RECORDS
WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE
EXEC PGM=SORT,PARM='RC16=NOABE' gives this-
Code:
WER131I PARM FIELD ERROR - RC16=NOA
WER276B SYSDIAG= 3338357, 4968406, 4968406, 4731549
WER164B 7,908K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 2,339,720 BYTES USED
WER146B 32K BYTES OF EMERGENCY SPACE ALLOCATED
WER108I SORTIN : RECFM=FB ; LRECL= 400; BLKSIZE= 27600
WER257I INREC RECORD LENGTH = 406
WER238I POTENTIALLY INEFFICIENT USE OF INREC
WER110I SORTOF01 : RECFM=FB ; LRECL= 400; BLKSIZE= 27600
WER410B 5,856K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,
WER410B 0 BYTES RESERVE REQUESTED, 2,192,264 BYTES USED
WER405I SORTOF01 : DATA RECORDS OUT 0; TOTAL RECORDS OUT
WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000
WER461A SORTOUT/OUTFIL DATA SET CONTAINS NO DATA RECORDS
WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE
//$ORTPARM DD * gives-
Code:
WER276B SYSDIAG= 3337043, 4968227, 4968227, 4731549
WER164B 7,908K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 2,339,720 BYTES USED
WER146B 32K BYTES OF EMERGENCY SPACE ALLOCATED
WER108I SORTIN : RECFM=FB ; LRECL= 400; BLKSIZE= 27600
WER257I INREC RECORD LENGTH = 406
WER238I POTENTIALLY INEFFICIENT USE OF INREC
WER110I SORTOF01 : RECFM=FB ; LRECL= 400; BLKSIZE= 27600
WER410B 5,856K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,
WER410B 0 BYTES RESERVE REQUESTED, 2,192,264 BYTES USED
WER405I SORTOF01 : DATA RECORDS OUT 0; TOTAL RECORDS OUT
WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000
WER461A SORTOUT/OUTFIL DATA SET CONTAINS NO DATA RECORDS
WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE
Joined: 21 May 2009 Posts: 139 Location: United States
yes CICS, I need RC as an indicator for next step. if RC16 doesnt work I'll use RC4. hope it wud be fine. but initially I was suggested a 16 only so just trying to go by that.
but can you guys have a look at one more thing-
Code:
POTENTIALLY INEFFICIENT USE OF INREC
is it bound to come ? or can we get rid of it somehow ?
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
t5590ag wrote:
yes CICS, I need RC as an indicator for next step. if RC16 doesnt work I'll use RC4. hope it wud be fine. but initially I was suggested a 16 only so just trying to go by that.
Then revisit an answer that has already been given...
CICS Guy wrote:
t5590ag wrote:
But can I use RC4 in place of RC16 ?
SyncSort for z/OS 1.3 Programmer’s Guide wrote:
NULLOFL Parameter (Optional)
Code:
RC0
NULLOFL=RC4
RC16
The NULLOFL parameter specifies the action to be taken when any non-SORTOUT OUTFIL data set contains no data records.
RC0 The delivered default instructs SyncSort to issue a return code of 0 if not overridden by a higher return code set for another reason.
RC4 Instructs SyncSort to issue a WER461I warning message and continue processing. A return code of 4 will be issued if not overridden by a higher return code set for another reason.
RC16 Instructs SyncSort to issue a WER461A message and to terminate processing with a return code of 16.
Quote:
but can you guys have a look at one more thing-
Code:
POTENTIALLY INEFFICIENT USE OF INREC
is it bound to come ? or can we get rid of it somehow ?
Joined: 21 May 2009 Posts: 139 Location: United States
hi, thats clear to me that RC16 has been assigned the ABEND in my system. but is it possible that i can override it somehow. I tried the options suggested by Arun already. And avoid the abend at RC16 and get it as return code of step for next step in job.
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
t5590ag wrote:
hi, thats clear to me that RC16 has been assigned the ABEND in my system. but is it possible that i can override it somehow.
And agan............
CICS Guy wrote:
t5590ag wrote:
yes CICS, I need RC as an indicator for next step. if RC16 doesnt work I'll use RC4. hope it wud be fine. but initially I was suggested a 16 only so just trying to go by that.
Then revisit an answer that has already been given...
CICS Guy wrote:
t5590ag wrote:
But can I use RC4 in place of RC16 ?
SyncSort for z/OS 1.3 Programmer’s Guide wrote:
NULLOFL Parameter (Optional)
Code:
RC0
NULLOFL=RC4
RC16
The NULLOFL parameter specifies the action to be taken when any non-SORTOUT OUTFIL data set contains no data records.
RC0 The delivered default instructs SyncSort to issue a return code of 0 if not overridden by a higher return code set for another reason.
RC4 Instructs SyncSort to issue a WER461I warning message and continue processing. A return code of 4 will be issued if not overridden by a higher return code set for another reason.
RC16 Instructs SyncSort to issue a WER461A message and to terminate processing with a return code of 16.
Quote:
but can you guys have a look at one more thing-
Code:
POTENTIALLY INEFFICIENT USE OF INREC
is it bound to come ? or can we get rid of it somehow ?
