Setting Up Background Job Information

ISMF stores Job Control Language (JCL) and execute statements in your profile. Each time you use a line operator or list command in normal mode that generates a background job, ISMF draws on this information to prime the job statement on the Job Submission Entry Panel.

ISMF does not do any validity checking of the JCL statements.

If you want to modify the job statements, you can specify this information in either of two ways:

From the ISMF Profile Option Menu. This procedure is described in Specifying Job Statements from the ISMF Profile Option Menu.
Before you submit your background job. This procedure is described in Specifying Job Statements when Submitting Jobs.

When you exit ISMF successfully, the JCL you enter for ISMF job statements is stored in your profile.

Specifying Job Statements from the ISMF Profile Option Menu

All the information that ISMF uses to process your background jobs is available from the ISMF Profile Option Menu (see Figure 1). With the options that are available, you can access the following information:

ISMF job statement information, option 2
DFSMSdss execute statement information, option 3
ICKDSF execute statement information, option 4
Data set print execute statement information, option 5
IDCAMS execute statement information, option 6

Specifying JCL on the ISMF Job Statement Entry Panel

Use the ISMF JOB STATEMENT option on the ISMF Profile Option Menu to establish a standard set of JCL statements for background jobs. Because this information is stored by ISMF in your profile, you only enter it once rather than each time you submit a job.

To set up the job statements in your profile, enter option 2, ISMF JOB STATEMENT, on the ISMF Profile Option Menu (shown in Figure 1). ISMF displays your ISMF Job Statement Entry Panel, as shown in Figure 1.

Figure 1. Specifying Job Statement Information

  Panel  Utilities  Help
--------------------------------------------------------------------------------
                        ISMF JOB STATEMENT ENTRY PANEL
Command ===>

Specify ISMF Job Statement Source . . 1
    1 ISPF
    2 ISMF
ISPF Job Statement Information
       //USERID   JOB  (ACCOUNT),'NAME'
       //*
       //*
       //*

ISMF Job Statement Information
  ===> //USER10A  JOB  (ACCOUNT),'NAME'
  ===> //*
  ===> //*
  ===> //*
  ===> //*
  ===> //*
  ===> //*
Use ENTER to Perform Verification;
Use HELP Command for Help; Use END Command to Save and Exit.

You can choose the source of your job control statements by selecting either ISMF or ISPF job control statements. If you select option 1, ISMF uses ISPF job statements to prime the Job Submission Entry Panel when submitting background jobs. If you choose option 2, the set of ISMF job control statements listed in the ISMF Job Statement Information field is used. Source 1 using ISPF job statements is the default.

The first time you invoke the Job Statement Entry Panel, ISMF provides a skeleton job statement for you to complete with ISMF JCL information. See Figure 1 for the format of the statement. ISPF job control statements are for display only and cannot be modified here. You can change them by using ISPF option 0.

Your user ID followed by the letter A appears as the job name. The A is an identifier for the current job. Each time you submit a background job the letter is incremented. For example, if the current job name is USER230A, the next job name will be USER230B. If you choose to substitute a number for the alphabetic identifier, 0 through 9 is used for the cycle. If you want to use a job name other than your user ID you can do so, but the following events will occur:

The name of each job you submit is not incremented by ISMF.
Your jobs cannot be found by the TSO STATUS command.

In addition, you might end up with jobs having the same name.

Restriction: Do not blank out the job name, because TSO does not generate a default job name.

The words ACCOUNT and NAME indicate the proper positions for you to supply accounting information and your name.

You can add up to six additional ISMF JCL statements to complete the Job Statement Entry Panel. These statements can be JOBLIB, JES2, JES3, or comment statements. Figure 2 shows an example of the JCL you can use to set up your profile for the ISMF version.

Figure 2. Sample JCL on the Job Statement Entry Panel

  Panel  Utilities  Help
--------------------------------------------------------------------------------
                        ISMF JOB STATEMENT ENTRY PANEL
Command ===>

Specify ISMF Job Statement Source . . 2
    1 ISPF
    2 ISMF
ISPF Job Statement Information
       //USERID   JOB  (ACCOUNT),'NAME'
       //*
       //*
       //*

ISMF Job Statement Information
  ===> //USER10A  JOB  (USER10,'B=050,D=M86,O=G42'),'USER.10',
  ===> //    USER=USER10,NOTIFY=USER10,
  ===> //    TIME=(0,15),MSGCLASS=Z,MSGLEVEL=(1,1),REGION=1024K
  ===> //*
  ===> //*
  ===> //*
  ===> //*
Use ENTER to Perform Verification;
Use HELP Command for Help; Use END Command to Save and Exit.

Related Reading: For more information on JCL syntax and parameters on the JOB statement, refer to z/OS MVS JCL Reference.

When you enter a list command or line operator and submit that job for background processing, the information from this profile panel is used to prime the Job Submission Entry Panel. See Specifying Job Statements when Submitting Jobs for more information on the Job Submission Entry Panels.

Specifying an Execute Statement for a DFSMSdss Background Job

To set up the DFSMSdss execute statement in your profile, enter option 3, DFSMSdss EXECUTE STATEMENT, on the ISMF Profile Option Menu (Figure 1). ISMF displays the DFSMSdss Execute Statement Entry Panel shown in Figure 3.

Figure 3. Skeleton Provided for the DFSMSdss Execute Statement

   Panel  Utilities  Help
 -------------------------------------------------------------------------------
                     DFSMSdss EXECUTE STATEMENT ENTRY PANEL
 Command ===>

 Specify DFSMSdss Execute Statement Information:

  ===> //*
  ===> //*
  ===> //**NOTE - THE REGION SIZE IS MINIMUM AND MAY BE CHANGED
  ===> //STEP1  EXEC  PGM=ADRDSSU,REGION=2048K
  ===> //*
  ===> //*
  ===> //SYSPRINT  DD  SYSOUT=*









 Use HELP Command for Help; Use END Command to Save and Exit.

The first time you invoke the DFSMSdss Execute Statement Entry Panel, ISMF provides a skeleton DFSMSdss EXEC statement for you to complete. The format of this statement is shown in Figure 3.

You can tailor this statement for your own use. You can add parameters to the DFSMSdss execute statement and up to five additional job steps before the DFSMSdss EXEC step. Make certain that the region size parameter is appropriate for your job and change it as necessary.

Figure 4 shows an example of how you can tailor the DFSMSdss execute statement to suit your needs.

Figure 4. Completed DFSMSdss Execute Statement

   Panel  Utilities  Help
 -------------------------------------------------------------------------------
                     DFSMSdss EXECUTE STATEMENT ENTRY PANEL
 Command ===>

 Specify DFSMSdss Execute Statement Information:

  ===> //*
  ===> //*
  ===> //*
  ===> //S1DFDSS EXEC PGM=ADRDSSU,REGION=2048K,
  ===> //  PARM='UTILMSG=YES,TYPRUN=SCAN'
  ===> //*
  ===> //SYSPRINT  DD  SYSOUT=*









 Use HELP Command for Help; Use END Command to Save and Exit.

The execute statement information in Figure 4 contains both an EXEC statement with added parameters and a data definition (DD) statement. The first line of the EXEC statement names the step (S1DFDSS), identifies DFSMSdss(PGM=ADRDSSU), and specifies the region size (REGION=2048K):

//S1DFDSS  EXEC PGM=ADRDSSU,REGION=2048K,

The second line contains parameter information:

//  PARM='UTILMSG=YES,TYPRUN=SCAN'

In the second line, UTILMSG=YES specifies that utility messages are to be printed in the SYSPRINT listing. TYPRUN=SCAN specifies that the JCL syntax for the job is checked and verified without actually executing the DFSMSdss function.

The last line contains a SYSPRINT statement that specifies that the SYSOUT class is the same as the MSGCLASS on the job statement:

//SYSPRINT DD SYSOUT=*

When you enter a list command or line operator that is submitted to DFSMSdss for processing, ISMF uses the information on the DFSMSdss Execute Statement Entry Panel to construct the DFSMSdss job stream. See Specifying Job Statements when Submitting Jobs for more details on submitting jobs for processing. To learn more about the DFSMSdss execute statement, see z/OS DFSMSdss Storage Administration.

Recommendation: Use the information from the DFSMSdss background job as a reference when you specify the ICKDSF, Data Set Print, and IDCAMS execute statements from the options listed on the ISMF Profile Option Menu (Figure 1).

Specifying Job Statements when Submitting Jobs

The Job Submission Entry Panel is primed with values from the Job Statement Entry Panel in your profile if you chose ISMF (option 2) as the job statement source. If you selected ISPF (option 1) from the Job Statement Entry Panel, the Job Submission Entry Panel is primed with values from the ISPF source job statements, which are displayed on the Job Statement Entry Panel for reference only.

The panel title of the Job Submission Entry Panel indicates the command or line operator you have specified. You can accept job statements, whether they are ISPF or ISMF job statements, or modify them for your immediate needs. When you press ENTER, the job is submitted using the JCL with any changes made.

Figure 5 is an example of the Job Submission Entry Panel you might see when you use the COPY command.

Figure 5. Sample Job Submission Entry Panel

   Panel  Utilities  Help
 ------------------------------------------------------------------------------
                           JOB SUBMISSION ENTRY PANEL
 Command ===>

 Select One of The Following
 2   1.  Submit Job for Background Processing
     2.  Save Generated Job in a Data Set
 If Save option is selected above, Specify:
  Data Set Name  . . .
  Replace Contents . . N             (Y or N)

 Job Statement Information:            (Verify before Proceeding)
       //USER10A  JOB (USER10,'B=050,D=M86,O=G48'),'USER10',
       //        MSGCLASS=Z,NOTIFY=USER10,USER=USER10,
       //        TIME=(0,5),MSGLEVEL=(1,1)
       //*
       //*
       //*
       //*
 Enter "/" to select option
 /  View or Change Execute Statements from Profile
 Use ENTER to Continue;
 Use HELP Command for Help; Use END Command to Exit.

After you complete the COPY Entry Panels, ISMF displays the COPY Job Submission Entry Panel. ISMF uses the information supplied on this panel to submit the COPY job to DFSMSdss. The fields on the panel and your options for completing them are:

SELECT ONE OF THE FOLLOWING

In this field, specify whether you want to submit a job immediately or to save the generated job stream in a data set.

Option: Meaning
1: ISMF uses the values you supplied on the data entry panels for the line operator or command and the information on the Job Submission Entry Panel and the DFSMSdss Execute Statement Entry Panel to generate the job stream and submit the job immediately for background processing.
2: ISMF generates the job stream and stores it in a data set. Saving a data set gives you the opportunity to look at the job stream before you actually submit the job.

If you choose option 2, you must complete the following fields:

DATA SET NAME: The data set must be preallocated, cataloged, and either physical sequential or partitioned. It may be a PDS member, a PDSE, or a relative generation data set. The data set must be fixed or fixed block and have a logical record length of 80.
REPLACE CONTENTS: This field specifies whether you want to replace any existing data with the new job stream or add the new job to the end of the data set.

JOB STATEMENT INFORMATION

The entries in this section of the panel can be either ISMF or ISPF job control statements depending on the source you specified on the ISMF Job Statement Entry Panel (see Figure 1). The entries provide processing parameters and accounting information, and identify ownership. With the ISMF version, you can add JOBLIB, JES2, JES3, or comment statements. You can have up to seven ISMF job control statements.

Guideline: While any changes made to ISMF job statements (source 2) are stored in your profile and used the next time you submit a background job, the changes made to ISPF job statements (source 1) are not saved in your profile. Changes to ISPF job statements are used only for current job submissions. A message about the status of your profile is displayed.

VIEW OR CHANGE EXECUTE STATEMENTS FROM PROFILE

In this field, indicate whether you want to display the DFSMSdss Execute Statement Entry Panel from your profile.

Option: Meaning
/: ISMF displays the DFSMSdss Execute Statement Entry Panel. You can verify or change the DFSMSdss execute statements before submitting the job.
blank: ISMF submits the job with the execute statements stored in your profile without showing them to you.

The DFSMSdss Execute Statement Entry Panel, shown in Figure 6, contains an example of an execute statement entry panel.

Figure 6. An Example of a DFSMSdss Execute Statement

   Panel  Utilities  Help
 -------------------------------------------------------------------------------
                     DFSMSdss EXECUTE STATEMENT ENTRY PANEL
 Command ===>

 Specify DFSMSdss Execute Statement Information:

  ===> //*
  ===> //*
  ===> //**NOTE - THE REGION SIZE IS MINIMUM AND MAY BE CHANGED
  ===> //STEP1  EXEC  PGM=ADRDSSU,REGION=2048K
  ===> //*
  ===> //*
  ===> //SYSPRINT  DD  SYSOUT=*









 Use HELP Command for Help; Use END Command to Save and Exit.

For individual jobs, you can add other steps before the execute statement (EXEC) and additional parameters to the EXEC step. Some useful parameters include:

TYPRUN=SCAN: Checks the JCL syntax without executing the DFSMSdss function.
UTILMSG=YES: Prints utility messages in the SYSPRINT listing.
PAGENO=nnnn: Indicates the starting page number for the SYSPRINT data set. nnnn can be any 1- to 4-digit number.
LINECNT=nnn: Indicates the number of lines to print per page. nnn can be any 1- to 3-digit number.
XABUFF=ABOVE16|BELOW16: Specifies whether the I/O buffer used for COPY, DUMP, and RESTORE is to be above or below the 16-megabyte virtual storage line.

For example, in Figure 6, the parameters on the EXEC statement specify that the listing should start on page 8 with 57 lines per page, and utility messages printed. z/OS DFSMSdss Storage Administration describes all the parameters that you can use.

Restriction: ISMF does not check the job statement or the DFSMSdss execute statement for validity. If you have a question about the correct way to specify a parameter, consult z/OS DFSMSdss Storage Administration.

Job Submission for Line Operators and Commands Entered in Last-Use Mode

If you enter a line operator in last-use mode (for example, COPY=), ISMF does not display the Job Submission Entry Panel. The processing options stored in your profile are used instead. If you chose to submit the last job immediately, the new job is sent directly to the job queue. If you chose to save the job stream in a data set the last time you submitted a background job, the new job is also saved. However, the new job is added to the end of the data set regardless of the option you specified the last time you used the Job Submission Entry Panel.