|
View previous topic :: View next topic
|
| Author |
Message |
hcl_ln
New User
Joined: 14 Sep 2005
Posts: 21
|
|
|
|
All -
May be this is a dumb Q, but wanted to see if there is a way around. 
I am trying to run a job using INTRDR, as below.
STEP1 & 2 are actually using INTRDR and STEP3 is actually using the files created from STEP1 & STEP2.
My job doesn't wait for STEP1 & STEP2 to be finished and STEP3 immediately kicks off, so gets a JCL error, because file not found.
Is there a way to correct this or does the INTRDR always the last step of the particular job?
| Code: |
//jobcard and job info ...
//*
//**********************************************************
//* use INTRDR-1
//**********************************************************
//STEP1 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DSN=A.B.C(mbr1),DISP=SHR
//SYSUT2 DD SYSOUT=(,INTRDR)
//*
//**********************************************************
//* use UNTRDR-2
//**********************************************************
//STEP2 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DSN=A.B.C(mbr2),DISP=SHR
//SYSUT2 DD SYSOUT=(,INTRDR)
//*
//*
//*****************************************************
//* FORMAT INTERNET RECORD TO ATTACHMENT RECORD LAYOUT
//*****************************************************
//STEP3 EXEC PGM=PGM1,COND=(0,NE)
//*****************************************************
//STEPLIB DD DSN=LOADLIB,DISP=SHR
// DD DSN=LOADLIB,DISP=SHR
//INDD DD DSN=A.B.C,DISP=SHR
//OUTDD DD DSN=A.B.C.D,
// DISP=(NEW,CATLG,CATLG)
// SPACE=.., UNIT=.., DCB=..
|
|
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
You may use INTRDR anywhere in a jobstream. It doesn't have to be the last step(s).
One way to do what you want is have step1 do what it does and then submit a job that is step2. Have the second job do what it needs to do and then submit a job that is step3. To keep them in line, use the same job name in each.
Is there some reason to use the INTRDR? It looks liike this could be done easily by actually running the "submitted" steps within the one job. |
|
| Back to top |
|
|
Bitneuker
CICS Moderator
Joined: 07 Nov 2005
Posts: 1104
Location: The Netherlands at Hole 19
|
|
|
|
Hi hcl_In,
First of all there are no dumb questions. We've all been there at the start of the 'new'.
Dick's answer is clear and correct. Just want to add 2 cents: same jobname will work fine under the condition (if I'm not mistaken) they are submitted into the same initiator/class.
@Dick: correct me if I'm wrong  |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hi George,
As far as i know and unless something has changed in the newest operating system(s), only 1 job of a given name will run at a time. This restriction is system-wide.
A few minutes go by. . . . .
Looked in the Fine Manual and found this:
| Quote: |
v For the job types TSO logon and batch processing, the jobname must be unique, otherwise:
? For TSO logon, duplicate jobnames fail. For example, if IBMUSER is logged on, another attempt to logon as IBMUSER will fail.
? For batch processing, duplicate jobnames are delayed. For example, if job BATCH01 is executing, then another job named BATCH01 will be delayed until the original job has completed. |
Additional $.02's always welcome - they tell me i'm a couple short. . .<g> |
|
| Back to top |
|
|
Bitneuker
CICS Moderator
Joined: 07 Nov 2005
Posts: 1104
Location: The Netherlands at Hole 19
|
|
|
|
Hi Dick,
I will check at our site; what I posted was 'from ancient memory'. I will get back to you and may be give you 2 dimes |
|
| Back to top |
|
|
|
|
