Starting a system task from a console

Naming considerations for started tasks

IBM® recommends that you use the JOBNAME parameter rather than an identifier. If you use the JOBNAME parameter, SMF records, messages, and automated programs can reflect or react to job status; identifiers can be viewed only at a console.

Syntax

 
S membername[.identifier]
  [,[devicetype|[/]devnum][,volumeserial]]
  [,parameters]
  [,JOBNAME=jobname]
  [,JOBACCT=acct_info]
  [,SUB=subsystemname]
  [,REUSASID=YES]
  [,keyword=option[,keyword=option]...]
 

Parameters

membername

The 1 - 8 character name of a member of a partitioned data set that contains the source JCL for the task to be started. The member can be either a job or a cataloged procedure. The subsystem that selects the job determines which JCL procedure library is called, usually MSTR, JES2 or JES3.

identifier

The name that identifies the task to be started. This name can be up to 8 characters long. The first character must be alphabetical. If you omit an identifier and the started task does not have an IEFRDER DD statement, the system uses the job name as the identifier.

If you omit an identifier and the started task has an IEFRDER DD statement, the device that is allocated to that started task becomes the identifier name.

Note: The system allows multiple started tasks with the same membername and identifier to run concurrently.

JOBNAME=jobname

The name that is assigned to the job.

• If the source JCL is a procedure and you omit the JOBNAME keyword, the member name is assigned as the job name.
• If the source JCL is a job and you omit the JOBNAME keyword, the system uses the job name that is assigned on the JOB statement in the JCL.

If you specify the JOBNAME keyword, the member name is used only to identify the member that contains the JCL for the started task.

If you specify the JOBNAME keyword, you cannot specify identifier.

JOBACCT=acct_info

An account number, and any other accounting information that your installation requires, such as your department and room number.

The JOBACCT parameter specifies accounting data in the JCL JOB statement for the started task. If the source JCL was a job and already accounting data, the value that is specified on the JOBACCT parameter overrides the accounting data in the source JCL.

For a detailed description of the accounting information format and syntax rules, see z/OS MVS JCL Reference.

The length of acct_info cannot exceed 55 characters.

devicetype

The device type of the output device (if any) associated with the task.

Note: devicetype and devnum are mutually exclusive. You cannot specify both parameters on a START command.

[/]devnum

The device number of the device to be started. A device number is 3 or 4 hexadecimal digits. A slash (/) must precede a 4-digit number but is not before a 3-digit number.

Note: devnum and devicetype are mutually exclusive. You cannot specify both parameters on a START command.

volumeserial

If devicetype is a tape or direct-access device, the volume serial number of the volume is mounted on the device.

parameters

Program parameters passed to the started program, which might be a list in parentheses or a string in single quotation marks. The documentation for the started program states the following techniques that the program supports:

• The fourth positional parameter on the START command. The program uses the QEDIT macro to get access to this parameter.
• The PARM keyword value. Register 1 at entry to the started program points to it.

If you are starting VTAM®, see z/OS Communications Server: SNA Operation.

SUB=subsystemname

The name of the subsystem that selects the task for processing. The name must be 1 - 4 characters, which are defined in the IEFSSNxx parmlib member, and the subsystem must be active. If SUB is not specified, the primary subsystem, as specified in IEFSSNxx, select the task.

Exception: If the name of the task that is started is the same as a subsystem, the task is started under the Master subsystem (MSTR). Then, any procedures started that is defined in the Job Entry subsystem's PROC00 data set but not in the MSTJCLxx data set, are unavailable and not found. The system then issues message IEFC612I. The only available procedure libraries in the Master subsystem are specified in the MSTJCLxx's IEFPDSI data set.

When the task that is started is a subsystem and you omit SUB, it is started under the master subsystem (MSTR). Except if the subsystem itself asks to start under the Job Entry subsystem, or the SSCTUPSS bit in the subsystem's SSCVT is on.

When you specify SUB, you override the subsystem's request as to the subsystem under which the task should be started.

Note: Do not specify SUB=MSTR unless the program specifically documents that it is supported. Using SUB=MSTR in a situation where it is not supported impacts the proper execution of the program.

REUSASID=YES

When REUSASID=YES is specified on the START command and REUSASID(YES) is specified in the DIAGxx parmlib member, a reusable ASID is assigned to the address space created by the START command. If REUSASID=YES is not specified on the START command or REUSASID(NO) is specified in DIAGxx, an ordinary ASID is assigned.

You can use REUSASID=YES for address spaces that result in message IEF352I ADDRESS SPACE UNAVAILABLE when they end. Before you specify REUSASID=YES, ensure that the program being started supports running with a reusable ASID. Otherwise, specifying REUSASID=YES might result in system abend 0D3. For more information about reusing ASIDs, see Reusing ASIDs in z/OS MVS Programming: Extended Addressability Guide.

keyword=option

Any appropriate keyword parameter that you specify to override the corresponding parameter in the cataloged procedure. The maximum length of each keyword=option is 66 characters. No individual value within this field can be longer than 44 characters in length. You can specify:

• JCL JOB statement keyword parameters to modify the JOB statement for the started task.
• JCL EXEC statement keyword parameters to override EXEC statements in the procedure started (if the target of the START command is a procedure)
• JCL DD statement keyword parameters to modify the IEFRDER DD statement (if it exists)
• JCL symbol names to provide values for use in the started task.

Parameters on JOB statements

JOB statement keyword parameters are accepted for both started jobs and started procedures. For started jobs, the keyword that is specified on the START command overrides or nullifies the corresponding keyword in the JCL.

You can specify the following job-level keywords:

• ADDRSPC
• BYTES
• CARDS
• CLASS (but it is ignored)
• COND
• DSENQSHR
• EMAIL
• GDBIAS
• JESLOG
• LINES
• MEMLIMIT
• MSGCLASS
• MSGLEVEL
• NOTIFY
• PAGES
• PERFORM
• PRTY
• REGION
• REGIONX
• TIME
• UJOBCORR

You cannot specify the source after job-level keywords, unless you code them with no values (to nullify the same keywords in the source JCL):

• USER
• USER
• GROUP
• PASSWORD
• RESTART
• SECLABEL
• SYSAFF
• SYSTEM
• TYPRUN

The system ignores the following keywords when they are specified on the START command, unless you code them with no values (to nullify the same keywords in the source JCL):

• RD
• CLASS
  Note: For a started task:

  • In a JES2 environment, the system ignores the CLASS keyword.
  • In a JES3 environment, the system ignores all CLASS related attributes and functions except for device fencing, SPOOL partitioning, and track group allocation.

Parameters on EXEC statements

EXEC statement keywords that have the same name as JOB statement keywords (for example, COND, REGION, and TIME), are treated as JOB statement keywords.

Note:

1. If you specify an option that must have lowercase characters, enclose it within apostrophes.
2. If you specify an option within apostrophes, for example, 'DUMMY', use the correct case letters within the apostrophes. The START command processing does not convert lowercase characters to uppercase. Thus, entering lowercase letters might cause a JCL error or an abend. Similarly, entering uppercase letters where lowercase is required (in z/OS® UNIX System Services, for example) might cause incorrect results.
3. If you are overriding a data set name in the cataloged procedure and the name of the data set is 44 characters long, use DSN=name. If you specify DSNAME=name, the START procedure stops and returns message IEF640I.
4. If you need information on started task considerations or use of overrides and symbols, see z/OS MVS JCL Reference.

Example 1

S jes2

Example 2

S JESNOW,JOBNAME=JES2,JOBACCT=(D548-8686,'12/8/85',PGMBIN)