On Thu, 12 Jul 2012 16:15:50 -0700, Lizette Koehler wrote:
>>
>>I know I could look at the input JCL and see it right there, but there is
>>a couple of thousand jobs involved here, and I would to find a better way.
>
>So I guess I would be curious as to what you are working on?
>Are you looking for validating JCL and scanning for certain text in the SYSIN?
>
>TYPRUN=SCAN is only JCL checking and so will not really "show" the output of
>the SYSIN.
>
TYPRUN=SCAN's "checking" is a bad joke. IIRC, it fails to report errors as
fundamental as DSNAME >44 characters. Somewhat better is TYPRUN=HOLD
and purge the job. I've been told that even that overlooks some errors that
can be detected statically. Perhaps still better is to insert:
//STEP0 EXEC PGM=IEFBR14
//SCAN IF FALSE THEN
...
//SCAN ENDIF
(itself a syntax error that the converter overlooks).
> Yes, in SDSF the SJ command can show it, but you indicate there are a couple
> of thousand jobs. So I am guessing you are looking for a REXX SDSF process
> to do "something". Can you elaborate?
>
Of course, if the OP has working JCL, there's no need to scan for syntax errors.
I have an EXEC based, IIRC, on an example in the SDSF tuna manual that
fetches all a job's JES data sets into a UNIX (USS) hierarchy. On a TYPRUN=SCAN
job these are:
user:156$ find JOBCARD.JOB02365
JOBCARD.JOB02365
JOBCARD.JOB02365/Job.
JOBCARD.JOB02365/Job./101..txt
JOBCARD.JOB02365/Job./103..txt
JOBCARD.JOB02365/Job./102..txt
JOBCARD.JOB02365/Job./1.JESJCLIN.txt
JOBCARD.JOB02365/Job./SJA.Reader.txt
JOBCARD.JOB02365/JES2.
JOBCARD.JOB02365/JES2./3.JESJCL.txt
JOBCARD.JOB02365/JES2./2.JESMSGLG.txt
JOBCARD.JOB02365/JES2./5.$INTTEXT.txt
and I find:
user:157$ cat JOBCARD.JOB02365/Job./SJA.Reader.txt
//JOBCARD JOB 505303JOB,'Paul Gilmartin', JOB02365
// MSGLEVEL=(1,1),REGION=0M,MSGCLASS=R,TYPRUN=SCAN
//*
//USERC OUTPUT JESDS=ALL,DEFAULT=YES,
// CLASS=R,PAGEDEF=V0648Z,CHARS=GT12
//*
//*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....|
//STEP EXEC PGM=IEFBR14
//*
Default SYSIN line
//*
//SYSUT1 DD *
Explicit sysin line
//*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....|
//
:w ! submit $MVS_HOST
... which appears identical to my submitted JCL, save for addition
of the JOB ID on the JOB statement. Interestingly, it even shows
test after the "//" line, which I thought was logical EOF.
Further,
user:158$ cat JOBCARD.JOB02365/JES2./3.JESJCL.txt
1 //JOBCARD JOB 505303JOB,'Paul Gilmartin',
JOB02365
// MSGLEVEL=(1,1),REGION=0M,MSGCLASS=R,TYPRUN=SCAN
//*
2 //USERC OUTPUT JESDS=ALL,DEFAULT=YES,
// CLASS=R,PAGEDEF=V0648Z,CHARS=GT12
//*
//*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....|
3 //STEP EXEC PGM=IEFBR14
//*
4 //SYSIN DD * GENERATED STATEMENT
//*
5 //SYSUT1 DD *
//*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....|
6 //
... shows the parsed JCL as it appears in the job output.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
