|
View previous topic :: View next topic
|
| Author |
Message |
kapiltamrakar
New User
Joined: 24 May 2009
Posts: 41
Location: Hyderabad
|
|
|
|
Hi all,
I am facing a issue.
In my JCL below steps are there
step1: runs rexx program. it generates DD DSN statement in a PDS member.
//XXXXXXXX JOB (XXXXXXXX),'AAAAAAA',
......
//PROC JCLLIB ORDER=(XXXXXX.TEST.PROCLIB)
//JOBLIB DD .....
//*
//RUNPRG EXEC PGM=IKJEFT01,PARM='TEMPDATE'
//SYSEXEC DD DSN=BBBBBB.MY.REXX,
// DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY
it generates text like below :
//DDREPORT DD DSN=ABABABA.D120418.T075211,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(TRK,(10,5),RLSE),
// UNIT=SYSDA,
// DCB=(BLKSIZE=8000,LRECL=80,RECFM=FB)
as you can see above file ABABABA contains current date and time.
in my rexx program, while writting the DD DSN statement, dataset name contains current date and time. which will be known run time.
Step2 : execute one cobol program which writes above file. so i have used "INCLUDE MEMBER= the above member name" for using that member name at run time.
//STEP010 EXEC PGM=COBOl program
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//DDCYC1 DD DSN=AAAAAA.INP,DISP=SHR
//DDCYC2 DD DSN=AAAAAA.INP1,DISP=SHR
// INCLUDE MEMBER=MEM1
//.....
...
now the problem come here :
at run time, my jcl step 2 is not picking the latest info at the member written by rexx. it picks the old info. i need my JCL step 2 which running the cobol program shoudl be picking latest info in the PDS member created by REXX.
Please help me in this.
thank you in advance.
Regards,
Kapil. |
|
| Back to top |
|
 |
daveporcelan
Active Member
Joined: 01 Dec 2006
Posts: 792
Location: Pennsylvania
|
|
|
|
What you are seeing is what is expected.
The resolution of the INCLUDE is done at JCL submission time.
It does not work the way you want it to.
You need to change your approach. |
|
| Back to top |
|
|
kapiltamrakar
New User
Joined: 24 May 2009
Posts: 41
Location: Hyderabad
|
|
|
|
| so, you mean, Inlcude wont pick the data at Run time, only submission time info would be final info for it? |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1787
Location: Bloomington, IL
|
|
|
|
| kapiltamrakar wrote: |
| so, you mean, Inlcude wont pick the data at Run time, only submission time info would be final info for it? |
Correct. As you are using Rexx to generate the INCLUDE member anyway, I recommend that you combine the two pieces of JCL by using file tailoring or, if you must, direct I/O, and submit that. |
|
| Back to top |
|
|
kapiltamrakar
New User
Joined: 24 May 2009
Posts: 41
Location: Hyderabad
|
|
|
|
Thank You Akatsukami and daveporcelan for your reply.
i have run my STEP 2 by INTRDR (submitting anotehr Job). now I am getting expacted results,
Thank you again 
Regards,
Kapil. |
|
| Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009
Posts: 1314
Location: Vilnius, Lithuania
|
|
|
|
| kapiltamrakar wrote: |
Thank You Akatsukami and daveporcelan for your reply.
i have run my STEP 2 by INTRDR (submitting anotehr Job). now I am getting expacted results. |
Of course this is unlikely to ever be accepted for a move to a production environment, as it opens a security hole large enough for a 747 to fly through. |
|
| Back to top |
|
|
kapiltamrakar
New User
Joined: 24 May 2009
Posts: 41
Location: Hyderabad
|
|
|
|
Hi Rob,
I didnt get your meaning. can you please explain? |
|
| Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006
Posts: 792
Location: Pennsylvania
|
|
|
|
In many shops the internal reader can not be used for production.
Allowing one Job to dynamically generate JCL and submit it, allows the transfer it's RACF (or ACF2) authority.
This is a security hole.
We need to use the scheduling package to do this type of thing.
Or keep your processing within a single Job. |
|
| Back to top |
|
|
kapiltamrakar
New User
Joined: 24 May 2009
Posts: 41
Location: Hyderabad
|
|
|
|
Hi dave,
Thank you for your answer, is this security issue also exists if we submit a Job thru Rexx? (either by generating jcl dynamically or a having static JCL in a dataset) and using Submit command.
Regards,
Kapil. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6248
Location: Mumbai, India
|
|
|
|
| kapiltamrakar wrote: |
| Thank you for your answer, is this security issue also exists if we submit a Job thru Rexx? (either by generating jcl dynamically or a having static JCL in a dataset) and using Submit command. |
Some one at your site should be addressing this, a Public Forum like this is not a good place to have an answer for such a question.
For an answer sake, it can be Yes or no - one might say, yes do it (as it serves your purpose) but all the consequences are yours, which might include from nasty e-mail communictions to, worse, the termination from Job. |
|
| Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006
Posts: 792
Location: Pennsylvania
|
|
|
|
As Anuj said, someone at your shop will have to answer.
At our site were are not allowed (unable) to submit Production Jobs thru INTRDR no matter how the JCL is generated. We must use our scheduling system.
In my opinion it is good policy, and a system exit enforces it. |
|
| Back to top |
|
|
kapiltamrakar
New User
Joined: 24 May 2009
Posts: 41
Location: Hyderabad
|
|
|
|
| Thank you Dave and Anuj for the information. |
|
| Back to top |
|
|
|
|
