Troubleshooting
Problem
Customer's DTF abended with S722 and noticed the NDMCMDS DD had produced a large amount of output.
Symptom
*SABA001I - DMTASSEL S722 U0000
Cause
The abend S722 is a result of one of the following output limits being exceeded:
- The output limit specified by the OUTLIM keyword on the SYSOUT DD statement
- The job output limit specified in the LINES and CARDS parameters of the JES2 JOBPARM statement
- The job output limit specified in the BYTES, CARDS, LINES, and PAGES parameters on the STANDARDS initialization statement or the JES3 MAIN statement
Diagnosing The Problem
Go to the NDMCMDS DD and look for messages similar to the following:
SIGNON NODE=10.224.131.65 USERID=(xxxxxxxx,)
PTION='1600 V04 Sterling Control Cent'.
.
.
SEL STAT WHERE( TYPE=(PI,ZI,CH,CI,DP,FP,FS,FT,IF,JI,NM,PS,PX,SB,SD,SI,IK,IT,ST,SW,TI,TS,UM,
UU,CT,MC,RJ,RT,ZT,PT,TF,TL,TW,QH,QE,QT,QW,CX) STARTT=(11/04/1984 23:29:51 ) STOPT=(11/04/1984 23:29:51 ) ) PNAME=xxxxxxxx FILE.
where the 'SEL STAT' is issued at regular intervals (e.g. every minute).
Resolving The Problem
The above 'SEL STAT' messages found at regular intervals in the NDMCMDS DD output is a result of Sterling Control Center's monitoring of Connect:Direct. To avoid the S722 abend, you could do one of the following:
(1) Check to see if you have the OUTLIM keyword specified on the NDMCMDS DD sysout statement and if so, increase the value.
(2) Contact your system programmer about getting the job output limit increased.
(3) Comment out the NDMCMDS DD statement. Please note if this is done and you have an issue that we need to see the contents of the NDMCMDS DD, you would have to add the NDMCMDS DD back and recreate the error.
Was this topic helpful?
Document Information
Modified date:
17 December 2019
UID
swg22011339