|
View previous topic :: View next topic
|
| Author |
Message |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
I found this job actually on our system as a real production job:
| Code: |
//P###### JOB (.,.....,....),'',CLASS=...,
// MSGCLASS=...,REGION=0M
//JOBLIB DD DSN=PROD....LOADLIB,DISP=SHR
//*
// SET TCSTRM='01'
// SET TYPE='R'
// SET FSETI='A'
// SET FSETO='A'
// SET QT=''''
// SET JOB='P#######'
// SET STRGRP='XXX'
// SET SP=' '
//CMD2FC2 EXEC PGM=...
// IF CMD2FC2.RC EQ 3000 THEN
// SET F2COPY='RR'
//*
//CHECKENQ EXEC CHECKENQ
//*
//FDRDEL EXEC FDRDEL
// SET F2COPY='01'
//FC2 EXEC FC2
// ENDIF
|
I wonder what they think it's supposed to be doing? |
|
| Back to top |
|
 |
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
//CHECKENQ EXEC CHECKENQ
//FDRDEL EXEC FDRDEL
//FC2 EXEC FC2
Without seeing what is in the 3 proc's being executed it would be hard to know (even after seeing them it would be hard to know).
Just guessing based on 'EXEC CHECKENQ' I would say it has something to do with check printing. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Maybe they're related to "FDR" (Innovation Data Processing)?
IAM File Processing?
www.fdr.com
Bill |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
The only thing in the CHECKENQ PROC is one step that executes IEFBR14. FDRDEL probably does run FDR.
I was thinking of their (improper) use of the variable F2COPY. I hope the job never actually needs it to be 'RR'. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
I really do not understand,
the only thing that is clear is that they are obfuscating things
I just run a quick test
| Code: |
000001 //ENRICO$A JOB CLASS=A,NOTIFY=&SYSUID,MSGCLASS=X
000002 // SET SUFF=AA
000003 //AMS EXEC PGM=IDCAMS
000004 //SYSPRINT DD SYSOUT=*
000005 //SYSIN DD *
000006 SET MAXCC = 8
000007 /*
000008 // IF AMS.RC = 4 THEN
000009 // SET SUFF=BB
000010 //BR14 EXEC PGM=IEFBR14
000011 // ENDIF
000012 //BR15 EXEC PGM=IEFBR14
000013 //NEW DD DISP=(NEW,CATLG),DSN=ENRICO.TEST.&SUFF,
000014 // SPACE=(CYL,(1,1,1)),
000015 // DCB=(RECFM=FB,LRECL=80)
|
and whatever is the MAXCC set by the IDCAMS Step SUFF will always hold BB
the set JCL statements are executed in sequence disregarding the IFs
to run quick and dirty tests for RC processing
the IDCAMS SET MAXCC is just great |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
Right. All SET statements are resolved during the scan, so no matter what happens the value of F2COPY will always be '01'. As far as I'm concerned the might as well place it up above with the rest of the SET statements.
I'm just suprised that they let those jobs slip into production like that. |
|
| Back to top |
|
|
|
|
