Hi Dave,
The JCLIN is not an actual job. It is just a bunch of statements which
get scanned for keywords, much like what recruiters do on LinkedIn.
I usually try to make sure that it is not executable in case in gets
SUBMITd accidentally.
Another thing, real Dataset Names are unnecessary. All that's needed is
the DDDEF name.
Here is how I code it:
++USERMOD(LMSIA38)
/* INSTALL CICS HPO (TYPE 6) SVC 255 (DFHHPSVC) TO NUCLEUS */ .
++VER(Z038) FMID(HBB7740).
++MOD(DFHHPSVC) LMOD(DFHHPSVC) LKLIB(SDFHLOAD) DISTLIB(SDFHLOAD).
++JCLIN.
//COPYSVC EXEC PGM=IEBCOPY
//SDFHLOAD DD DSN=SDFHLOAD
//NUCLEUS DD DSN=NUCLEUS
C I=((SDFHLOAD,R)),O=NUCLEUS
S M=((DFHHPSVC,,R))
On 2021-03-22 11:51, Dave Jousma wrote:
Jerry,
I wouldnt move it, just write a usermod to copy it to NUCLEUS, and update your
NUCLSTxx member. Let the CICS guy tell you when it changes, and you need to
re-apply your usermod.
We incidentally dont install DFHHPSVC. Not sure why, I did ask the CICS guy
about it.
Here is an old copy of a usermod i had laying around
++USERMOD(MCIC001) .
++VER(Z038) FMID(HBB7707) . 00036000
++JCLIN. 00037000
//JOB1 JOB 'DFHHPSVC',MSGLEVEL=(1,1)
//STEP1 EXEC PGM=IEBCOPY
//ESALINK DD DSN=SYS1.ZOS15.LINKLIB,DISP=SHR,UNIT=3390,
// VOL=SER=TSG005
//NUCLEUS DD DISP=SHR,DSN=SYS1.NUCLEUS,UNIT=3390,VOL=SER=TGT10A
//SYSIN DD *
COPY INDD=ESALINK,OUTDD=NUCLEUS TYPE=MOD
SELECT M=(DFHHPSVC)
/* 00050000
++MOD(DFHHPSVC) LKLIB(LKLIB). 00051000
QX 00052000
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
