Doubt about TYPRUN parameter
Sandeep Reddy
Dear Sir,
Please clear my doubt about TYPRUN parameter in JCL...
TYPRUN = SCAN--------------?
TYPRUN = HOLD--------------?
TYPRUN = RUN-----------------?
TYPRUN = COPY-------------?
TYPRUN = JCLHOLD--------?
TYPRUN = (if any)-------------?
Thanks and regards
B.Sandeep Reddy
9502015861
Sundarram TE
Wish you all a very happy Sankaranthi.
TYPRUN=SCAN - checks the JCL for syntax errors and suppresses execution of the job You may use this optional parameter to check your JCL for syntax errors.
TYPRUN=HOLD - JES checks the syntax and holds the JCL in the input queue for later execution. It is held until the operator or the owner releases it.
TYPRUN=COPY (JES2 only) - The job stream is printed as a SYSOUT data set but not processed.
TYPRUN=JCLHOLD (JES2 only) - Similar to HOLD, but the job is held before its JCL is scanned rather than after.
TYPRUN=RUN - Default Value
Hope it is clear now. You may try them and verify, so that it will be more clear.
With best wishes
TESM
TESM
Please post your queries on the Forum only, as we may have others also who have similar questions or queries.
Ok. coming to your query about PERFORM and RD parameters .
PERFORM:
PERFORMance groups are defined by the Inatallation, that are associated with specific CLASS of jobs. Default GROUPs are defined by the installation. If you want to override the performance group associated with the job class, however, you can specify the PERFORM parameter on a JOB or EXEC statement.
Keep in mind, though, that if you include a PERFORM parameter on a JOB statement, it overrides any PERFORM parameters specified on EXEC statements.
The syntax for the PERFORM parameter of the JOB and EXEC statements
PERFORM=group
Explanation group An installation-defined performance group with a value from 1 to 999.
The effect of the PERFORM parameter depends on the workload management mode, WLM compatibility mode
it’s a good idea to check that with your systems programmer (Administrator) before using the PERFORM parameter.
The PERFORM parameter in the JOB or EXEC statement specifies a performance group for the job or step. If a PERFORM parameter isn’t coded, the system uses an installation default if there is one. Otherwise, it uses a built-in system default of 1 for non-TSO/E job steps and 2 for TSO/E sessions.
A JOB statement that uses the PERFORM parameter
OS/390 and Z/OS JCL
//MM02D JOB (36512),'G MURACH',PERFORM=10
An EXEC statement that uses the PERFORM parameter
//APRCALC EXEC PGM=APRCALC,PERFORM=3
Description
- The PERFORM parameter assigns a job or step to a performance group defined by the installation.
- Each performance group has performance characteristics associated with it that determine the rate at which jobs or steps have access to theprocessor, storage, and channels. For example, a performance group can control how frequently a job or step’s address space can be swapped in and out.
- Although the PERFORM parameter can be used in either WLM compatibility mode or WLM goal mode, more than likely, your installationwill have it configured to run in WLM compatibility mode.
- If a PERFORM parameter isn’t specified on a JOB or an EXEC statement, the default performance group assigned to the job class is used.
- A PERFORM parameter specified on a JOB statement applies to all the steps within the job and overrides any PERFORM parameters specified on EXEC statements.
OS/390 provides two parameters for restarting a job. The RESTART parameter can be coded on the JOB statement to handle job failures, while the RD parameter can be coded on the JOB or EXEC statement to handle job or system failures. In addition, JES2 and JES3 both provide statements that restart jobs automatically in case of a system failure.
RESTART can be coded on the JOB statement, with a STEPname. Whereas RD can be coded on both JOB as well as STEP. RD is associated with CHECK POINTS that you create thru your COBOL, PL/I or Assembler programs.( Useful when you have large volume of data to be processed) In COBOL you have Clause RURUN, that can br coded on I-O-CONTROL paragraph in INPUT-OUTPUT SECTION.
Examples of the RD Parameter
Example 1
//STEP1 EXEC PGM=GIIM,RD=R
RD=R specifies that the operator can perform automatic step restart if the job step fails.
Example 2
//NEST EXEC PGM=T18,RD=RNC
RD=RNC specifies that, if the step fails, the operator can perform automatic step restart. RD=RNC suppresses automatic and deferred checkpoint restarts.
Example 3
//CARD EXEC PGM=WTE,RD=NR
RD=NR specifies that the operator cannot perform automatic step restart or
automatic checkpoint restart. However, a CHKPT macro instruction can establish checkpoints to be used later for a deferred restart.
Example 4
//STP4 EXEC PROC=BILLING,RD.PAID=NC,RD.BILL=NR
This statement calls a cataloged or in-stream procedure BILLING. The statement specifies different restart requests for each of the procedure steps: PAID and BILL.
On Thursday, 10 January 2013 10:19:15 UTC+5:30, Sandeep Reddy wrote:
Chunawala, Quasar
Hi Sandeep,
I know that service classes are defined in WLM, each with different goals. Are these different from the perform groups that you've talked about in the below e-mail?
Quasar Chunawala
Senior Developer
iNautix Technologies Pvt. Ltd., Pune
The BNY Mellon Company,
E-mail: qchun...@inautix.co.in Ph: 020-66217000 Extn: 2118 VOIP: 22174
--
You received this message because you are subscribed to the Google Groups "Mainframes 360" group.
To post to this group, send email to
mainfr...@googlegroups.com.
To unsubscribe from this group, send email to
mainframes36...@googlegroups.com.
Visit this group at
http://groups.google.com/group/mainframes360?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
******************************************************
This message and any files or attachments sent with this message contain confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute, copy or use any part of this email. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return Email.
Email transmission cannot be guaranteed to be secure or error-free as information can be intercepted, corrupted, lost, destroyed, late, incomplete or may contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission.
******************************************************