I have to make a new member in a JCL. This isn't a problem:
My code:
//STEP1 EXEC PGM=IEBGENER
//SYSUT1 DD *
//SYSUT2 DD DISP=(NEW,KEEP),UNIT=SYSALLDA,DSN=name.JCL4(MEMBER),
SPACE=(CYL,(1,1,45)),
VOL=SER=DMTU01
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
/*
But I want that my MEMBER1 contains text.
So when I go in JCL4 and I press an e (edit) before MEMBER, I want to see some text like 'Hallo'. Can someone help me to explain how to do this?
If you are creating a new member in an existing JCL dataset, Try:
//STEP1 EXEC PGM=IEBGENER
//SYSUT1 DD *
Hello
/*
//SYSUT2 DD DSN=name.JCL4(MEMBER),DISP=(SHR,KEEP)
//SYSIN DD DUMMY
/*
The Disp refers to the dataset and not the member. so if the dataset already exists, you do not need to create it !!.
If you want create a new JCL dataset and a member at the same time,
the JCL should be like (where you catlg the dataset)
//STEP1 EXEC PGM=IEBGENER
//SYSUT1 DD *
Hello
/*
//SYSUT2 DD DSN=name.JCL4(MEMBER),DISP=(NEW,CATLG),
// UNIT=SYSALLDA, should this be sysda ???
// SPACE=(CYL,(1,1,45)),
// VOL=SER=DMTU01
//SYSIN DD DUMMY
/*
Related
I have a main program which is purely COBOL, and a COBOL-DB2 subprogram. I compiled both using a cobol-db2 compiler, return code is 4 (informational warning only). Then, I bind them both. Now I'm trying to execute the main program using a JCL DB2, however, it doesn't seem to be able to call the subprogram or even execute the run step.
This is my JCL DB2 to run the mainprog calling the subprog:
//GO EXEC PGM=IKJEFT01,DYNAMNBR=20,REGION=4M,COND=(4,LT)
//STEPLIB DD DSN=DSN910.DB9G.RUNLIB.LOAD,
// DISP=SHR
// DD DISP=SHR,DSN=DSN910.DB9G.SDSNEXIT
// DD DISP=SHR,DSN=DSN910.SDSNLOAD
// DD DISP=SHR,DSN=ISP.SISPLOAD
// DD DISP=SHR,DSN=GDDM.SADMMOD
//SYSOUT DD SYSOUT=*
//SYUDUMP DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//TRANFILE DD DSN=PROJECT.ABC.TRANKSDS,DISP=SHR
//MGMTREPT DD DSN=PROJECT.ABC.MGMTREPT,
// UNIT=SYSDA,DISP=(NEW,CATLG),
// SPACE=(32,(3,3)),
// DCB=(RECFM=FB,LRECL=81,BLKSIZE=81)
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DB9G)
RUN PROGRAM(ABCREPRT) PLAN(DSNTIA91)
END
/*
Then this is the SDSF of the JCL, return code = 0:
NP DDNAME StepName ProcStep DSID
JESMSGLG JES2 2
JESJCL JES2 3
JESYSMSG JES2 4
Shouldn't GO stepname appear as well if it's a successful execution?
I would at least expect a READY message on //SYSTSPRT if that step did start. So, yes there should be an entry for SYSTSPRT in that list. Did you look at the OUTPUT queue in SDSF to see if some output of your job went to this queue instead of the HOLD queue?
You could replace the DSN ... END sequence in //SYSTSIN with some TSO command, say LISTA and see if this produces some output.
In the following JCL, the HFS path /u/woodsmn/jjk does not exist. It raises a JCL error and does not run the COPYHFS step, nor any other steps. I want it to detect the missing file, and run the FAILIND step.
I suspect MVS raises a JCL error and completely ignores any COND conditions that might apply. I was hoping it raise some failure step condition code and behave that way.
How can I re-write this to execute steps when a PATH does not exist?
//WOODSMN1 JOB (1111),MSGLEVEL=(1,1),CLASS=A,MSGCLASS=H,
// USER=WOODSMN,REGION=1M
//COPYHFS EXEC PGM=IKJEFT01
//INHFS DD PATH='/u/woodsmn/jjk',
// PATHOPTS=(ORDONLY),RECFM=VB,LRECL=255,BLKSIZE=32760
//OUTMVS DD DSN=WOODSMN.TESTDS1,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(TRK,(1,1)),
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=8080)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
OCOPY INDD(INHFS) OUTDD(OUTMVS) CONVERT(NO)
/*
//*
//NETVIEW EXEC PGM=IEFBR14,COND=(0,EQ,COPYHFS)
//*
//SUCCIND EXEC PGM=IEBGENER,REGION=1M,COND=(0,EQ,NETVIEW)
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD *
Attempt to put file succeeded
/*
//SYSUT2 DD PATHOPTS=(ORDWR,OTRUNC,OCREAT),PATHMODE=SIRWXU,
// PATHDISP=(KEEP,DELETE),
// PATH='/u/woodsmn/TESTDS.SUCCESS'
//SYSIN DD DUMMY
//*
//FAILIND EXEC PGM=IEBGENER,REGION=1M,COND=(0,GT,NETVIEW)
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD *
Attempt to put file failed
/*
//SYSUT2 DD PATHOPTS=(ORDWR,OTRUNC,OCREAT),PATHMODE=SIRWXU,
// PATHDISP=(KEEP,DELETE),
// PATH='/u/woodsmn/TESTDS.FAIL'
//SYSIN DD DUMMY
//
Use BPXBATCH to execute a shell command to test the existence of your directory.
//EXIST001 EXEC PGM=BPXBATCH,PARM='SH test -e /u/woodsmn/jjk'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
You may have to get a bit more exotic and use the STDPARM DD to pass a `set -o errexit' to get the return code to work exactly as you wish.
Two things to change:
Firstly, run IKJEFT1B instead of IKJEFT01, because the former will end when a command in SYSTSIN ends with a non-zero returncode, and that return code will become the step return code.
Secondly, allocate the z/OS UNIX file with the ALLOC command just before the OCOPY. ALLOC will return with RC=12 if it cannot allocate the file (for whatever reason).
So, your first step should look like this:
//COPYHFS EXEC PGM=IKJEFT1B
//OUTMVS DD DSN=WOODSMN.TESTDS1,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(TRK,(1,1)),
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=8080)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
ALLOC F(INHFS) PATH('/u/woodsmn/jjk') -
PATHOPTS(ORDONLY) RECFM(V B) LRECL(255) BLKSIZE(32760)
OCOPY INDD(INHFS) OUTDD(OUTMVS) CONVERT(NO)
/*
You can then test the return code from the COPYHFS step as usual. (And btw, you don't need that NETVIEW step, but instead test the return code from the COPYHFS step directly.)
IKJEFT1B, as well as IKJEFT01, and the third variation IKJEFT1Aare described in Appendix A. Executing the terminal monitor program in the manual z/OS TSO/E Customization.
I have the following code:
//******************************************
//PROC01 EXEC PGM=IEBGENER
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD SYSOUT=(B,SMTP)
//SYSUT1 DD *
RCPT TO:<MAIL#AR.TEST.COM>
DATA
SOME TEXT GOES HERE
Can I attach a dataset/file into the mail? Thanks.
Try something like:
//******************************************
//PROC01 EXEC PGM=IEBGENER
//EMAIL OUTPUT DEST=EMAIL,
// USERDATA=('FILENAME:attachment.txt',
// 'TO:<MAIL#AR.TEST.COM>',
// 'FILEDESC:Sent from MVS'),
// TITLE=('Sent from MVS'),
// MAILFROM=('<YOURMAIL#AR.TEST.COM>'),
// REPLYTO=('<YOURMAIL#AR.TEST.COM>')
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD SYSOUT=Z,OUTPUT=*.EMAIL
//SYSUT1 DD DISP=SHR,DSN=<DSNNAME>
or, if you would like the attachment to be a PDF, something like:
//******************************************
//PROC01 EXEC PGM=IEBGENER
//EMAIL OUTPUT DEST=EMAILPDF,
// USERDATA=('FILENAME:attachment.pdf',
// 'TO:<MAIL#AR.TEST.COM>',
// 'PDFPGSIZ=(826,1169)',
// 'PDFFONT=(COURIER,8)',
// 'FILEDESC:Sent from MVS'),
// TITLE=('Sent from MVS'),
// MAILFROM=('<YOURMAIL#AR.TEST.COM>'),
// REPLYTO=('<YOURMAIL#AR.TEST.COM>')
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD SYSOUT=Z,OUTPUT=*.EMAIL
//SYSUT1 DD DISP=SHR,DSN=<DSNNAME>
Hope this works for you :)
You should be able to just add card:
// DD DSN=,DISP=SHR
to the end of your existing job. We use this style all the time. Using the OUTPUT card is also an option, as previously noted.
I am trying to understand where I am going wrong in my JCL file.
Here is my code as follows:
//MULTG013 JOB 1,NOTIFY=&SYSUID
//STEP1 EXEC PGM=ICEGENER
//SYSUT1 DD DSN=UNTG013.DATAIN(AUTODATA),DISP=SHR
//SYSUT2 DD DSN=UNTG013.DATAOUT(MULTIOUT),DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//STEP2 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE UNTG013.DATAIN(AUTONEW)
/*
//STEP3 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//OLDINV DD DSN=UNTG013.DATAIN(AUTODATA),DISP=SHR
//NEWINV DD DSN=UNTG013.DATAIN(AUTONEW),DISP=SHR
//SYSIN DD *
REPRO INFILE(OLDINV) OUTFILE(NEWINV)
/*
//STEP4 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//STUFF DD DSN=UNTG013.DATAIN(AUTONEW),DISP=SHR
//SYSIN DD *
PRINT INFILE(STUFF) CHAR
/*
//STEP5 EXEC PGM=IKJEFT01
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
RENAME 'UNTG013.DATAIN(AUTONEW)' 'UNTG013.DATAIN(ITDSDATA)'
/*
//STEP6 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//STUFF DD DSN=UNTG013.DATAIN(ITDSDATA),DISP=SHR
//SYSIN DD *
PRINT INFILE(STUFF) CHAR
/*
//STEP7 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE UNTG013.DATAIN(ITDSDATA)
/*
//
The error I am getting on the SYS Z is: IEFC605I UNIDENTIFIED OPERATION FIELD, lines 17 & 25.
Not quite sure how it is incorrect. Thanks
OK. Here is the message from spool:
SDSF OUTPUT DISPLAY MULTG013 JOB02122 DSID 4 LINE NOT PAGE MODE DATA
COMMAND INPUT ===> SCROLL ===> PAGE
***************** TOP OF DATA ******************
STMT NO. MESSAGE
17 IEFC605I UNIDENTIFIED OPERATION FIELD
25 IEFC605I UNIDENTIFIED OPERATION FIELD
**************** BOTTOM OF DATA ****************
also just found this as well.
SDSF OUTPUT DISPLAY MULTG013 JOB02122 DSID 2 LINE NOT PAGE MODE DATA
COMMAND INPUT ===> SCROLL ===> PAGE
***************** TOP OF DATA ******************
J E S 2 J O B L O G -- S Y S T E M S 0 W 1 -- N O D E
17.59.22 JOB02122 ---- FRIDAY, 28 MAR 2014 ----
17.59.22 JOB02122 IRR010I USERID UNTG013 IS ASSIGNED TO THIS JOB.
17.59.22 JOB02122 IEFC452I MULTG013 - JOB NOT RUN - JCL ERROR 415
------ JES2 JOB STATISTICS ------
41 CARDS READ
45 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
2 SYSOUT SPOOL KBYTES
0.00 MINUTES EXECUTION TIME
**************** BOTTOM OF DATA ****************
Hope this helps and thanks for the input thus far! I am still looking into it as well to see if I can figure it out on my own.
When looking at the source of your JCL as posted on SO I see TABs between //STUFF and DD in the two STUFF-lines. If they are there in your original JCL as well try replacing them by spaces. With JCL Blanks and TABs are not interchangeable.
I tried to run this following JCL program using IBM z/OS
//PAYMENT JOB MSGCLASS=H
//PAYMENT EXEC PGM=PAYMENT,REGION=1024K
// PARM='CSQ1,CARD.PAYMENTS,IND0163.REPLY,IND0163
// 5999.99,"MY PAYMENT"'
//STEPLIB DD DSN=ZOS.CONTEST3.PART2.LOAD,DISP=SHR
// DD DSN=WMQ.V6R0.SCSQLOAD,DISP=SHR
// DD DSN=WMQ.V6R0.SCSQANLE,DISP=SHR
// DD DSN=WMQ.V6R0.SCSQAUTH,DISP=SHR
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
but after submission of the job ,when I'm trying to view the job output using SDSF , I'm getting IEFC605I UNIDENTIFIED OPERATION FIELD on line 3 and 4 !! can anyone tell me what's wrong with my program ...
Try ending lines 2 and 3 with a comma so the JCL reader knows that these lines are not yet complete (ie. continue on the following line).
//PAYMENT JOB MSGCLASS=H
//PAYMENT EXEC PGM=PAYMENT,REGION=1024K, <== continued...
// PARM='CSQ1,CARD.PAYMENTS,IND0163.REPLY,IND0163, <== continued...
// 5999.99,"MY PAYMENT"'
//STEPLIB DD DSN=ZOS.CONTEST3.PART2.LOAD,DISP=SHR
// DD DSN=WMQ.V6R0.SCSQLOAD,DISP=SHR
// DD DSN=WMQ.V6R0.SCSQANLE,DISP=SHR
// DD DSN=WMQ.V6R0.SCSQAUTH,DISP=SHR
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//SYSPRINT DD SYSOUT=*