|
STOP Command Use the STOP command to stop system functions and jobs in execution. Note that you can communicate with the currently running program only if it was designed to recognize the STOP command. If the program does not recognize the STOP command, MVS issues message IEE342I STOP REJECTED--TASK BUSY. Note to Programmers: For more information, see the section on communicating with a program using EXTRACT and QEDIT in OS/390 MVS Programming: Authorized Assembler Services Guide. The following figure lists tasks the STOP command can perform. Use it as an index to details about particular uses of the command. Table 4-37. Summary of the STOP Command Topic: Command: "Stopping an Address Space" STOP jobname.identifier "Stopping an ASCH Initiator" on page 4-501 STOP ASCHINT "Stopping the Data Lookaside Facility (DLF)" on page 4-501 STOP DLF "Stopping the Library Lookaside (LLA) Address Space" on page 4-501 STOP LLA "Stopping the Object Access Method (OAM) Address Space" on page 4-502 STOP OAM "Stopping a System Object Model (SOM)" on page 4-502 STOP SOM "Stopping the Virtual Lookaside Facility (VLF)" on page 4-503 STOP VLF Syntax The syntax for each variation of the STOP command is shown immediately preceding its respective parameter list. STOP or P Stopping an Address Space You can use the STOP command to stop an address space. Note that you can communicate with the currently running program only if it was designed to recognize input from the STOP command. If the program does not recognize the input specified on the STOP command, MVS issues message IEE342I STOP REJECTED--TASK BUSY. Note to Programmers: For more information, see the section on communicating with a program using EXTRACT and QEDIT in OS/390 MVS Programming: Authorized Assembler Services Guide. P [jobname.]identifier[,A=asid] Parameters The parameters are: jobname The name of the job. The name of an address space is determined based on whether the JOBNAME= keyword was specified on the START command. If JOBNAME= was specified, jobname is the name assigned to the address space. If JOBNAME= was not specified and the source JCL for the address space is:
The identifier assigned to the job or address space. (Refer to "Displaying Started Task Status" on page 4-147 for information about determining the jobname and identifier of currently active address spaces.) The following types of identifiers can be used:
A device number is 3 or 4 hexadecimal digits, optionally preceded by a slash (/). You can precede the device number with a slash to prevent ambiguity between the device number and a device type or identifier. v devicetype, the type of device specified when the START or MOUNT command was issued. If no identifier was specified, the identifier "STARTING" is temporarily assigned until the system can assign another according to the following order of precedence:
When (and only when) you specify jobname with identifier, the identifier can be represented by any of the following:
When you use the asterisk format, the command takes effect on all address spaces that begin with the specified characters. Device numbers are assumed to be 4-digit numbers; for example, /13* would match on 1301, 1302, and so on, but would not match on 13C. Specifying both the job name and the entire identifier causes the command to take effect on all the work units running with that combination of job name and identifier. If you are uncertain of an identifier or device number:
A=asid The address space identifier, in hexadecimal, of the job, started task, writer, transaction program, or initiator address space to be stopped. If you issue a STOP command with a non-unique identifier, device name, or device type, multiple tasks might be stopped. To make sure that the STOP command stops only one task, add a unique job name to the START command membername; use that same unique job name on the STOP command. If you enter the STOP command and one or more terminals are still active, you are asked to respond to the following message: * id IKT010D nn USERS ACTIVE — REPLY 'SIC' or 'FSTOP' Reply ‘* *SIC’ to cancel the active users normally. This reply allows them to receive any messages queued for them, and it allows TSO/VTAM to perform its normal termination processing. Reply ‘FSTOP’ to force immediate cancellation of the active users. The users do not receive any messages queued for them, and TSO/VTAM does not perform its normal termination processing (that is, task resource manager processing is bypassed). Use FSTOP only if ‘SIC’ is ineffective. STOPMN Command Use the STOPMN command to stop the continual display of job status, data set status, or time-sharing user session activity initiated in response to the MONITOR command or MONITOR parameters on the CONSOLE and INIT statements in the CONSOLxx member of SYS1.PARMLIB. Syntax The complete syntax for the STOPMN command is: STOPMN or PM PM {JOBNAMES[,L={a|cc|cca|name|name-a}]} {DSNAME } {SPACE } {STATUS[,L={a|cc|cca|name|name-a}] } {SESS[,L={a|cc|cca|name|name-a}] } Parameters The parameters are: JOBNAMES Stop the jobname display specified in the MONITOR JOBNAMES command. DSNAME Stop the display of non-temporary data set names specified in the MONITOR DSNAME command. SPACE Stop the display of available space on direct access volumes specified in the MONITOR SPACE command. STATUS Stop the display of data set names, volume serial numbers, and status specified in the MONITOR STATUS command. SESS Stop the display of time-sharing user identifiers. L=a, cc, cca, name, or name-a The console where the display is to appear unless routing instructions are in effect. See the MSGRT command in this chapter. If you omit this keyword, the display appears at the console at which you enter the PM command. Example: To discontinue the display of job name information that appears when a job is initiated or stopped, enter: PM JOBNAMES Use the STOPTR command to halt or reduce the information periodically displayed as a result of the TRACK command. Scope in a Sysplex The STOPTR command has sysplex scope only when you specify L=. See "Using Commands That Have Sysplex Scope" on page 1-10 for more about sysplex scope. Syntax The complete syntax for the STOPTR command is: STOPTR or PT PT {TS }[,L={a }] {JOBS} {cc } {J } {cca } {A } {name } {name-a} Parameters The parameters are: TS Stop the display of active time-sharing users. JOBS or J Stop the display of active jobs, active Advanced Program-to-Program Communication/MVS (APPC/MVS) transaction programs, MOUNT commands in execution, and active tasks. A Stop the display of active jobs, active APPC/MVS transaction programs, active time-sharing users, MOUNT commands in execution, and active tasks. L=a, cc, cca, name, or name-a The display area (a), console identifier (cc), both (cca), console name (name), or both (name-a) of the active MCS console where the display appears. STOPTR is not valid for extended MCS consoles or system consoles. If you omit this operand, the command affects the dynamic display on the console through which the command is entered unless routing instructions are in effect; see the MSGRT command in this chapter. Note: TRACK A followed by STOPTR TS or STOPTR JOBS has the same effect as TRACK JOBS or TRACK TS. Example 1 To discontinue the periodic display of system status information directed to area A of console 22, enter: pt a,l=22a Example 2 To display the number of starts, mounts, jobs, time-sharing users, and a list of jobs, including APPC/MVS transaction programs (but not time-sharing users), enter: TR A,L PT TS |
The information on this site is the combined effort of a lot of people,
please credit the authors if you use their information.
|