MVSFORUMS.com

baskkarsubbian · Beginner Joined: 31 Aug 2003 Posts: 18 Topics: 12

Can we code anything before job statement in ajcl?

What is Restart st and where should be it coded? what is the diff between RD parameter of the step and Restart?

kolusu · Posted: Mon Sep 01, 2003 8:07 am Post subject:

baskkarsubbian,

Yes you can code COMMENTS before a JOB Statement in JCl.

RESTART parameter is used to indicate the step, procedure step, or checkpoint at which the system is to restart a job. You can specify that the system perform either of two restarts:

1.Deferred step restart, which is a restart at the beginning of a job step.

2.Deferred checkpoint restart, which is a restart from a checkpoint taken during step execution by a CHKPT macro instruction.

check this link for a detailed explanation of the restart parameter with examples.

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B631/20.23?DT=20030423085347

Hope this helps...

cheers

kolusu

baskkarsubbian · Beginner Joined: 31 Aug 2003 Posts: 18 Topics: 12

Hi,

Other than comments can we code anything before the job statement?

What is RD keyword parameter of the EXEC statement.

What's the diff between RD and Restart? Question

Brian · Beginner Joined: 12 Aug 2003 Posts: 95 Topics: 6

Kolusu,

I am afraid if we can code "comments" before the first valid JOB statement in a JCL. If my memory serves me right the JES considers the //* line itself as a JOB card and submits it (only to end with a JCL ERROR).

I can't access my box now. Can someone confirm this.

kolusu · Posted: Tue Sep 02, 2003 6:16 am Post subject:

baskkarsubbian,

Check this link for a detailed explanation of RD parameter

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B631/16.12?DT=20030423085347

You can cause a deferred checkpoint/restart(Restart=) of a job by the following procedure:

Use the option of coding a special form of the RD parameter (RD=NR) in the original job. This specifies that, if the CHKPT macro instruction executes, a checkpoint entry is written but an automatic checkpoint/restart is not requested. Omission of RD=NR will not preclude a deferred checkpoint/restart.

Cause execution of the CHKPT macro instruction, which writes checkpoint entry.

Resubmit the job whether or not it terminated abnormally. For example, resubmit it because a volume of one of its input data sets was in error and had caused the corresponding part of an output data set to be in error.

Code the RESTART parameter (RESTART=(stepname,checkid)) on the JOB statement of the restart job. The parameter specifies both the step to be restarted and the checkid that identifies the checkpoint entry to perform the restart.

Place a SYSCHK DD statement immediately before the first EXEC statement in the restart job. It specifies the checkpoint data set from which the specified checkpoint entry is read and is additional to any DD statements in the job that define data sets into which checkpoint entries are written.

Brian: You can code comments before the Job statement and JES intreprets it as a job without a jobcard and ends with "job has no steps" as the system automatically generates the jobcard. if you do not code a jobcard at all , the job runs fine with the system generated jobcard.

Hope this helps...

cheers

kolusu

Mike · Posted: Tue Sep 02, 2003 6:07 pm Post subject:

Brian,
comment statements before the jobcard are legal, however if you use the submit command, this itself doesn't like (using my default options) statements that precede the jobcard. I think it sees a non JOB statement and kindly then adds a job statement, the result actually being the submission of two jobs. The first one (i.e. the new job resulting from the submit command adding a job card on your behalf), will then fail as it contains no steps. The real job, (i.e. from the original job statement on) will run as a job.

If you submit a job that submits a second job to the internal reader and this second job includes a preceding comment then this works fine, other than you get something like $HASP125 INTRDR SKIPPING FOR JOB CARD FROM JOB14235 DMI021AA (i.e. JES doesn't really like what you've done so it ignores it).

In fact I went a little further and submitted the following job using the submit command :-

Brian · Beginner Joined: 12 Aug 2003 Posts: 95 Topics: 6

Kolusu Mike

Thanks for the clarification.

kolusu · Posted: Wed Sep 03, 2003 6:03 am Post subject:

Mike,

I firmly beleive that /*XMIT statement should be immediately after a JOB statement.

Check this link for confirmation

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B631/27.14.4?SHELF=&DT=20030423085347

The only JES2 command which can precede a job statement is /*PRIORITY Statement and Jes3 command is //**PAUSE

Most shops restrict the users from using them

Kolusu

vkrishna2001 · Posted: Wed Sep 03, 2003 12:22 pm Post subject:

If CA-7 submits the job then a comment before the job statement is not acceptable.

Vijay

Mike · Posted: Wed Sep 03, 2003 5:34 pm Post subject:

Kolosu,
sorry you're right it's been ages since I've used XMIT (personally I always used /*XEQ) and got confused by the requirement that the job statement of an instream job initiated via /*XMIT must follow the /*XMIT statement.
_________________
Regards,
Mike.

whizkid79 · Beginner Joined: 29 Sep 2004 Posts: 53 Topics: 14

Hi all,

How can i use Restart parameter along with PL/I PLICKPT parameter. I believe i need to use a SYSCHK DD in the JCL. I tried all this stuff but, nothing gets written to the SYSCHK file. Can you tell me the exact procedure of logging an checkpoint in a file and restarting from that point using JCL and PL/I.