/STOP Command: ADS through MADSIOT >>-+-/STOP-+----------------------------------------------------> '-/STO--' >--+-ADS--ddname-----------------------------------+----------->< +-APPC--+--------+------------------------------+ | '-CANCEL-' | | .----------. | | V | .-LOCAL--. | +-AREA--+---areaname-+--+--------+-+--+-------+-+ | | '-GLOBAL-' | '-NOPFA-' | | | .-LOCAL-. | | | '-ALL--+-------+-----------' | +-AUTOARCH--------------------------------------+ +-BACKUP--+--------+----------------------------+ | '-ABDUMP-' | | .------. | | V | | +-CLASS--+---cls#-+-+---------------------------+ | '-ALL------' | | .--------. | | V | .-LOCAL--. | +-DB--+---dbname-+--+--------+-+--+-------+-----+ | | '-GLOBAL-' | '-NOPFA-' | | | .-LOCAL-. | | | '-ALL--+-------+---------' | +-DATAGRP--datagroupname--+-------+-------------+ | '-LOCAL-' | +-DESC------------------------------------------+ +-DC--------------------------------------------+ | .-------. | | V | | +-LINE--+---line#-+--------------------+--------+ | | .--------. | | | | V | | | | +-line#--PTERM--+---pterm#-+-+-+ | | | '-ALL--------' | | | '-ALL--------------------------' | | .----------------. | | V | | +-LTERM--+---+-ltermname--+-+-+-----------------+ | | '-ltermname*-' | | | '-ALL----------------' | | .--------. | | V | | +-LU--+-+---luname-+-+--+-INPUT--+-+------------+ | | '-ALL--------' '-OUTPUT-' | | | | .--------. | | | | V | | | | '-luname--TPNAME----tpname-+-' | '-MADSIOT---------------------------------------'
STOP Command: MSNAME through SURV >>-+-/STOP-+----------------------------------------------------> '-/STO--' .-------------. V | >--+-MSNAME--+---+-msname--+-+-+-----------------------------+->< | | '-msname*-' | | | '-ALL-------------' | | .---------------. | | V | | +-NODE--+---+-nodename--+-+----------------+--------------+ | | '-nodename*-' | | | | .----------. | | | | V | | | | +-nodename--USER--+---username-+-+-+ | | | '-ALL----------' | | | '-ALL------------------------------' | +-OLDS--olds#---------------------------------------------+ +-OTMA----------------------------------------------------+ | .---------. | | V | | +-PGM--+---pgmname-+-+------------------------------------+ | '-ALL---------' | | .---------------------. | | V | | +-REGION--+---reg#--+-----------+-+---------------------+-+ | | '-reg#-reg#-' | | | +-reg#--+-ABDUMP--tranname------+-------------+ | | | +-TRANSACTION--tranname-+ | | | | '-CANCEL----------------' | | | | .---------. | | | | V | | | | +-JOBNAME----jobname-+------------------------+ | | '-JOBNAME--jobname--+-ABDUMP--tranname------+-' | | +-TRANSACTION--tranname-+ | | '-CANCEL----------------' | | .---------. | | V | | +-RTC--+---rtcname-+-+------------------------------------+ | '-ALL---------' | +-SB------------------------------------------------------+ +-SERVGRP-------------------------------------------------+ +-SLDSREAD------------------------------------------------+ | .------------. | | V | | +-SUBSYS--+---subsysname-+-+------------------------------+ | '-ALL------------' | | .-ALL-. | '-SURV--+-----+-------------------------------------------' +-LNK-+ +-LOG-+ '-RDS-'
STOP Command: THREAD through XRCTRACK .------. V | >>-+-/STOP-+--+-THREAD--+---reg#-+------------------------+-+-->< '-/STO--' | '-reg#--+-ABDUMP--tranname------+-' | | +-TRANSACTION--tranname-+ | | '-CANCEL----------------' | +-TMEM--tmembername--TPIPE--+-tpipename-+-----+ | '-ALL-------' | | .---------------. | | V | | +-TRAN--+---+-tranname--+-+------------+------+ | | '-tranname*-' | | | '-ALL--+---------------------+-' | | | .------. | | | | V | | | | '-CLASS--+---cls#-+-+-' | | '-ALL------' | | .---------------. | | V | | +-USER--+---+-username--+-+-+-----------------+ | | '-username*-' | | | '-ALL---------------' | +-VGR-----------------------------------------+ +-WADS--wads#---------------------------------+ '-XRCTRACK------------------------------------'
Table 157 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.
Command / Keywords | DB/DC | DBCTL | DCCTL |
---|---|---|---|
/STOP | X | X | X |
ABDUMP | X | X | X |
ADS | X | X | |
APPC | X | X | |
AREA | X | X | |
AUTOARCH | X | X | X |
BACKUP | X | X | |
CANCEL | X | X | X |
CLASS | X | X | |
DB | X | X | |
DATAGRP | X | X | |
DESC | X | X | |
DC | X | X | |
GLOBAL | X | X | |
INPUT | X | X | |
JOBNAME | X | X | X |
LINE | X | X | |
LOCAL | X | X | |
LTERM | X | X | |
LU | X | X | |
MADSIOT | X | X | |
MSNAME | X | X | |
NOPFA | X | X | |
NODE | X | X | |
OLDS | X | X | X |
OTMA | X | X | |
OUTPUT | X | X | |
PGM | X | X | X |
PTERM | X | X | |
REGION | X | X | X |
RTC | X | X | |
SB | X | X | |
SERVGRP | X | X | X |
SLDSREAD | X | X | X |
SUBSYS | X | X | X |
SURV | X | X | |
THREAD | X | X | |
TMEM | X | X | |
TPIPE | X | X | |
TPNAME | X | X | |
TRAN | X | X | |
USER | X | X | |
VGR | X | X | |
WADS | X | X | X |
XRCTRACK | X | X | X |
The /STOP command stops:
For VTAM nodes, the currently connected terminal is disconnected. All further logons are rejected until the node is the subject of a /START or /RSTART command.
The /STOP command can be used on HALDBs. For more information see High Availability Large Database Commands
/STOP validity checks all parameters entered by the terminal operator. If an error is detected on parameters that are independent of one another, only the invalid parameters are indicated as being in error and the /STOP command processes the rest of the parameters.
/STOP can be used to reset conditions previously established by the /START, /RSTART, /PSTOP, /PURGE, or /MONITOR commands.
Although the /STOP ADS command has no option of LOCAL/GLOBAL, if the DEDB area is shared at the block level, the response is the same as if GLOBAL were specified.
The output of the /STOP ADS command is changed when the command is entered through the OM API. In this case, the DFS058I message is not returned to OM. The command response returned to OM contains one or more of the following messages as appropriate.
Fast Path messages: DFS140I, DFS0488I, DFS0666I, DFS1407I, DFS3720I, DFS3721I, DFS3771I
/STOP APPC sets the desired status to STOPPED. The current status is set to STOPPED or FAILED according to the response from APPC/MVS.
/STOP APPC CANCEL sets the desired status to CANCEL according to responses from APPC/MVS. If the desired status is DISABLED. then IMS rejects /STOP APPC CANCEL2 when it is entered.
The output of the /STOP AREA command is changed when the command is entered through the OM API. In this case, the DFS058I message is not returned to OM. For commands that specify GLOBAL, only the command master returns the asynchronous messages to OM. When a command is processed with the LOCAL keyword, all IMSs are able to return the asynchronous messages to OM. The command response returned to OM contains one or more of the following messages as appropriate.
Fast Path messages: DFS140I, DFS170I, DFS0488I, DFS0666I, DFS1407I, DFS3062I, DFS3342I, DFS3720I, DFS3824I
/STOP AREA is not supported on an RSR tracking subsystem.
The GLOBAL keyword and the ALL parameter are mutually exclusive. If both keywords are specified, the command is rejected. The GLOBAL keyword requires that IRLM be active. If IRLM is not active, the command is rejected. DBRC is informed that the database or area has been stopped and will update the RECON data set to indicate the stopped condition.
The GLOBAL keyword is not supported on an RSR tracking subsystem.
If the GLOBAL keyword on a command is entered from an OM API, the command should only be routed to one IMS system in the IMSplex. The IMS that receives the command from OM will make DBRC calls to update the RECON with GLOBAL status. It will also request IRLM NOTIFY to route and process the command on sharing IMS systems, and then process the command locally.
Messages produced on the NOTIFIED systems will appear only on the system console and will not be routed back to the OM API which originally entered the command.
If multiple IMS systems have been explicitly specified in the route list, the master IMS system will process the command as described previously. However, the non-master IMS systems, to which OM routes the command, will reject the command with the following return and reason code listed in Table 158:
Return Code | Reason Code | Meaning |
---|---|---|
X'00000004' | X'00001000' | The command contained the GLOBAL keyword and was routed to more than one IMS system in the IMSPLEX. The non-master IMS systems will reject this command when OM routes the command to them. The master IMS system will process this command and use IRLM NOTIFY to route and process the command on the non-master IMS systems. See the discussion under the GLOBAL keyword. |
Recommendation: Before restarting the database or area, issue this command without the NOPFA keyword to inform DBRC of the change in status for the database or area.
All regions currently handling transactions assigned to the specific class are allowed to run until the limit count is reached (MPPs) or the input queue contains no more messages (BMPs and MPPs).
The region is not allowed to wait for the next message (wait-for-input mode). Instead a QC status code (no more messages) is returned to the application (MPPs).
If the region is already scheduled and waiting for the next message (wait-for-input mode) when the command is entered, the region is notified and a QC status code is returned to the application. (MPPs).
A batch message processing region (BMP) scheduled against wait-for-input (WFI) transactions returns a QC status code (no more messages) for /PSTOP REGION, /DBD, /DBR, or /STA commands only.
If the database is a DEDB or MSDB, programs using the database will not be scheduled. For other databases, the programs will still be scheduled but a call against the database will result in either a 3303 pseudoabend, or a BA status code, if the INIT call was issued.
If the database is stopped after the region is scheduled, the region is not allowed to wait for the next message (wait-for-input mode). If there are no more messages available for the region to process, a QC status (no more messages) will be returned to the application (MPPs). If the region is already scheduled and waiting for the next message (wait-for-input mode) when the command is entered, the region is notified and a QC status code is returned to the application (MPPs).
A batch message processing region (BMP) scheduled against wait-for-input (WFI) transactions returns a QC status code (no more messages) for /PSTOP REGION, /DBD, /DBR, or /STA commands only.
In an IFP region, the /STOP command has no effect until the region is started again.
See the AREA keyword for a description of the LOCAL, GLOBAL, and NOPFA keywords.
For DBCTL, when CCTL schedules a PSB, the DBCTL thread SCHED request defines the thread as LONG or SHORT. If the database is currently scheduled to a LONG thread, the command is rejected; otherwise, the thread is allowed to complete before the database is acted upon. This results in either a commit point or transaction termination.
For the results of issuing this command on a shared secondary index, see Shared Secondary Index Database Commands
/STOP DATABASE is not supported on an RSR tracking subsystem.
The output of the/STOP DATABASE command is changed when the command is entered through the OM API. In this case, the DFS058I message is not returned to OM. The command response returned to OM contains one or more of the following messages as appropriate to the database type and the command completion.
Full Function Database messages: DFS132, DFS160, DFS216, DFS0488I, DFS1407, DFS2026, DFS3318I, DFS3466I
Fast Path Database messages: No unique messages are returned.
Related Reading: See Group Parameters for more information on defining data groups.
During /STOP DATAGROUP processing, all virtual storage option (VSO) DEDBs that are in a z/OS data space are removed from the data space and updates are written out to DASD.
Recommendation: Although you can use DBDS groups as well as database groups for this command, you should use database groups whenever possible to eliminate the overhead of converting the DBDS group to a database group.
The /STOP DC command can be used either before or after the /CLSDST NODE or /STOP NODE command, the only difference being that logons can still |occur if the /STOP DC command is not entered. However, the command cannot start |or complete processing if the VTAM ACBs (APPLID and MNPS) are not |open or the VTAM nodes remain active. If the nodes are active, the /CLSDST NODE or /STOP NODE command must be issued to close the nodes; in some cases, |a /IDLE NODE command can be issued to cause an OS VTAM VARY command to |be issued against any nodes that remain connected.
/STOP LINE PTERM ensures that no input messages from any of the specified terminals assigned to the specified lines will be received by IMS after the command is issued.
/STOP LINE resets preset mode, test mode, response mode, lock pterm, lock lterm, pstop lterm, and purge lterm because these statuses are not significant and therefore are not kept after a /START LINE or restart.
If IMS internally resets the QLOCK condition, the LTERM remains in a STOPPED state. (QLOCK indicates that the LTERM is locked from sending any further output or from receiving input that can create additional output for the same LTERM until the state is reset by a specific request received on the session.)
/STOP LTERM is rejected for remote logical terminals.
The LTERM parameter can be generic where the generic parameter specifies LTERMs that already exist.
If global resource information is kept in Resource Manager, the /STOP LTERM command stops messages from being queued to the lterm anywhere in the IMSplex and the change is reflected both in Resource Manager and in the local IMS system.
Specifying the keyword INPUT with the LUNAME TPNAME keyword stops an luname for any input and synchronous outbound activities. Specifying the parameter ALL with INPUT causes all future LU 6.2 input and synchronous outbound activities to be stopped as well.
Specifying the keyword OUTPUT with the LUNAME TPNAME keyword stops an luname for any asynchronous outbound activities. Specifying the parameter ALL with OUTPUT causes all future LU 6.2 asynchronous outbound activities to be stopped as well.
Specifying neither INPUT nor OUTPUT is the same as specifying both INPUT and OUTPUT. The LU name is stopped for any input, and both synchronous and asynchronous outbound activities. Specifying the parameter ALL in this case stops all future LU 6.2 inbound activities, synchronous and asynchronous outbound activities.
A network-qualified LU name is optional for the LUNAME keyword. If the LU name is not network-qualified and no TP name is specified, all network-qualified LU names whose LU names match the LU name specified are also stopped.
/STOP LUNAME TPNAME stops a particular TP name of the LU name specified.
If the specified resource does not exist, a structure is created to retain the status.
DFS12761 MADS I/O TIMING FUNCTION STOPPED SUCCESSFULLY/START MADSIOT allows users to resume the MADS I/O timing function.
If MADS I/O Timing list structure is not defined in DFSVSMxx, the command will be rejected. If MADS I/O Timing function is already disabled, the command will be ignored. If MADS I/O Timing function is enabled and all sharing partners successfully disconnect from MADS I/O Timing list structure on the coupling facility, the command will complete successfully; if any sharing partners fails to disconnect to MASD I/O Timing list structure, the command will fail.
The output of the/STOP MADSIOT command is changed when the command is entered through the OM API. In this case, the DFS058I message is not returned to OM. The command response returned to OM contains one or more of the following messages as appropriate.
Fast Path messages: DFS0023I, DFS0008I, DFS1271I, DFS1276I, DFS1275E, DFS1219E
The /STOP NODE command prevents future logons until a /START NODE command is issued.
/STOP NODE without the USER keyword is supported for nodes that do not yet exist. It causes the node to be created and stopped which prevents the dynamic node from logging on. /STOP NODE without the USER keyword affects all half-sessions of the specified node.
/STOP NODE USER is valid for ISC and non-ISC nodes and users; however the user must still be allocated or signed on to the node. /STOP NODE USER for ISC nodes stops the named half-session defined in USER username for NODE nodename.
/STOP NODE resets preset mode, test mode, response mode, lock node, lock lterm, pstop lterm, and purge lterm because these statuses are not significant and therefore are not kept after a logon or restart. /STOP NODE also takes other actions depending on the recovery settings for the node:
If global resource information is kept in Resource Manager, the /STOP NODE command sets a global stop status for the node and prevents the node from logging on anywhere in the IMSplex. If global resource information is not kept in Resource Manager, /STOP NODE creates the node, if it does not exist in an ETO environment, and sets stop status for the local node. If the node does not exist in a non-ETO environment, the /STOP NODE command is rejected.
If in dual mode, both primary and secondary OLDSs are stopped. If there are only two OLDS data sets available, or if the specified OLDS is the one currently being used for output, the /STOP OLDS command will be rejected.
/STOP OTMA command processing is as follows:
/STOP PROGRAM does not stop CPI Communications driven transaction programs.
/STOP REGION reg# can also be used to terminate Fast Path regions. /STOP REGION reg# cannot be used to terminate batch regions.
A Fast Path utility region is terminated at the next system checkpoint of the utility.
The region identifier is reg# and the transaction code is tranname.
If the transaction indicated by tranname is currently running in REGION reg#, an error message is received at the master terminal, indicating an application program abend. The region is still be active but the transaction is stopped. The command is ignored if the transaction is not currently scheduled in region reg#.
|/STOP REGION reg# ABDUMP should be used only for a region that appears to be looping |or in a wait state. If this command does not abnormally terminate the |application running in a region, then the /STOP REGION reg# CANCEL command can be used. This might cause the control region |to terminate with abend 113 if parallel DL/I is being used. See /STOP REGION reg# CANCEL for further warnings.
|If the /CHECKPOINT command cannot shut down IMS because a message processing |region appears to be active, but in actuality is no longer active |in the system (a condition commonly referred to as a phantom region), |the /STOP REGION reg# ABDUMP command can be used to correct the situation. In this case, |the /STOP REGION reg# ABDUMP command detects that the region is no longer active and cleans |the internal IMS entries for the non-existent region, which allows |the shut down process to proceed normally.
|If a message processing region experiences a catastrophic |failure and abnormally terminates and a /DISPLAY ACTIVE REGION shows the region is still defined to IMS, the /STOP REGION reg# ABDUMP command can be used to correct the situation. In this case, |the /STOP REGION reg# ABDUMP command detects the region is no longer active and cleans |the internal IMS entries for the none-existent region.
The tranname variable is not valid for batch, IFP, or Fast Path utility regions.
The region identifier is reg# and the transaction code is tranname.
If the transaction indicated by tranname is currently running in region reg#, the IMS message DFS0569I is received at the master terminal, indicating that a QC status code (no more messages) was returned to the application program (MPPs). The region that contained the application is still active and the transaction is not stopped. A batch message processing program in WFI mode must be stopped using the /PSTOP command.
A batch message processing region (BMP) scheduled against wait-for-input (WFI) transactions returns a QC status code (no more messages) for, /PSTOP REGION, /DBD, /DBR, or /STA commands only.
The region identifier is reg#.
Using the /STOP REGION CANCEL command can cause the IMS control region to terminate with user abend 113 if parallel DL/I is being used. A z/OS CANCEL command will be rejected.
Once communications are stopped, the logger stops sending log data to the RSR tracking subsystem. No more attempts to re-establish failed conversations are made at OLDS switch. /STOP SERVGRP is normally not needed. /STOP SERVGRP is valid from an active subsystem and a tracking subsystem.
Successful completion of the syntax checking of the /STOP SERVGRP command results in the DFS058 STOP COMMAND COMPLETED message, although processing of the command continues asynchronously.
/STOP SUBSYS can also be used to dynamically reconfigure existing subsystem definitions. The operator can issue the /STOP SUBSYS command, change or add to the PROCLIB member, and then issue the /START SUBSYS command. IMS attempts to connect those subsystems defined in the PROCLIB member.
If system failure occurs after /STOP SUBSYS is processed, the stopped status is still set.
The /STOP THREAD command is not valid for:
While processing the /STOP TMEMBER TPIPE command, IMS creates a temporary transaction pipe (if one does not already exist) with the stopped status. IMS sets the synchronization status for this transaction pipe when it sends or receives the first message for the transaction pipe.
After a /STOP TMEMBER xxx TPIPE ALL command is issued, newly created tpipes will not be stopped for either input or output.
If the region is already scheduled and waiting for the next message (wait-for-input mode) when the command is entered, a QC status (no more messages) is returned to the application (MPPs). If there are no more messages available for the region to process, the region is not allowed to wait for the next message. Instead, a QC status is returned to the application (MPPs).
A batch message processing region (BMP) scheduled against wait-for-input (WFI) transactions returns a QC status code (no more messages) for /PSTOP REGION, /DBD, /DBR, or /STA commands only.
In a shared-queues environment, if you issue a /STOP TRANSACTION command for a transaction that is not defined on that IMS subsystem, IMS creates an SMB if the Output Creation user exit routine indicates the destination is a valid transaction. The SMB is marked as "dynamic".
A dynamic SMB created by a /STOP TRANSACTION command can only be used to queue messages for the transaction and place the messages on the shared queues. The transaction cannot be scheduled or assigned. IMS does process checkpoints for the transaction, but does not save them across an IMS restart if they do not have a valid status.
The TRANSACTION parameter can be generic, when the generic parameter specifies a transaction that already exists.
For ISC users, /STOP USER specifies the ISC user that is to be made unavailable for allocation until a /START USER command is issued.
For signed on users, the /STOP USER command prevents future signons until a /START USER command is issued.
/STOP USER is supported for users that do not yet exist. It causes the user to be created and stopped, which prevents the dynamic user from signing on.
/STOP USER will not cause the user to be signed off if the associated node is not active or the associated node is not in session.
The /STOP USER command for an ETO user session resets status that is not significant such as preset mode, test mode, response mode, lock lterm, pstop lterm, and purge lterm.
/STOP USER for ETO users also takes other actions depending on the recovery settings for the user:
If global resource information is kept in Resource Manager, the /STOP USER command sets a global stop signon status for the user and prevents the user from signing on anywhere in the IMSplex. If global resource information is not kept in Resource Manager, /STOP USER creates the user, if it does not exist in an ETO environment, and sets stop status for the local user. If the user does not exist in a non-ETO environment, the /STOP USER command is rejected.
While this command prevents VTAM from routing new sessions using a generic resource name to the IMS subsystem, it does not affect existing sessions, and affinities remain (until terminated through normal processing).
Entry ET:
/STOP AREA DB1AREA0 DB1AREA1
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS0488I STOP COMMAND COMPLETED. AREA=DB1AREA0 DFS0488I STOP COMMAND COMPLETED. AREA=DB1AREA1
Explanation: The DEDB areas DB1AREA0 and DB1AREA1 are stopped for processing.
Entry ET:
/STOP AUTOARCH
Response ET:
DFS058I STOP COMMAND COMPLETED
Explanation: Automatic archiving is stopped.
Entry ET:
/STOP CLASS 3
Response ET:
DFS058I STOP COMMAND COMPLETED
Explanation: No further scheduling of application programs for class 3 transactions occurs. All message processing programs currently handling class 3 transactions are allowed to run until the processing limit count is reached or the input queue contains no more messages.
Entry ET:
/STOP DATABASE TREEFARM
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS0488I STOP COMMAND COMPLETED. DBN=TREEFARM RC=0
Explanation: Database TREEFARM is stopped.
TSO SPOC input:
STO DB BANKATMS BANKTERM BANKLDGR BE3ORDER
TSO SPOC output:
SYS3 DFS0488I STO COMMAND COMPLETED. DBN= BANKATMS RC= 0 SYS3 DFS0488I STO COMMAND COMPLETED. DBN= BANKTERM RC= 0 SYS3 DFS0488I STO COMMAND COMPLETED. DBN= BANKLDGR RC= 0 SYS3 DFS0488I STO COMMAND COMPLETED. DBN= BE3ORDER RC= 0 IMS3 DFS0488I STO COMMAND COMPLETED. DBN= BANKATMS RC= 0 IMS3 DFS0488I STO COMMAND COMPLETED. DBN= BANKTERM RC= 0 IMS3 DFS0488I STO COMMAND COMPLETED. DBN= BANKLDGR RC= 0 IMS3 DFS0488I STO COMMAND COMPLETED. DBN= BE3ORDER RC= 0
OM API input:
CMD ( STO DB BANKATMS BANKTERM BANKLDGR BE3ORDER )
OM API output:
<?xml version="1.0"?> <!DOCTYPE imsout SYSTEM "imsout.dtd"> <imsout> <ctl> <omname>OM1OM </omname> <omvsn>1.1.0</omvsn> <xmlvsn>1 </xmlvsn> <statime>2002.197 22:05:21.270547</statime> <stotime>2002.197 22:05:21.307712</stotime> <staseq>B7EFC16AF6B13F26</staseq> <stoseq>B7EFC16AFFC40D8C</stoseq> <rqsttkn1>USRT005 10150521</rqsttkn1> <rc>00000000</rc> <rsn>00000000</rsn> </ctl> <cmd> <master>SYS3 </master> <userid>USRT005 </userid> <verb>STO </verb> <kwd>DB </kwd> <input>STO DB BANKATMS BANKTERM BANKLDGR BE3ORDER </input> </cmd> <msgdata> <mbr name="SYS3 "> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BANKATMS RC= 0</msg> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BANKTERM RC= 0</msg> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BANKLDGR RC= 0</msg> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BE3ORDER RC= 0</msg> </mbr> <mbr name="IMS3 "> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BANKATMS RC= 0</msg> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BANKTERM RC= 0</msg> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BANKLDGR RC= 0</msg> <msg>DFS0488I STO COMMAND COMPLETED. DBN= BE3ORDER RC= 0</msg> </mbr> </msgdata> </imsout>
Explanation: The STOP command is routed from OM to the two active IMSs - SYS3 and IMS3. The response from both IMSs is returned to OM. The databases BANKATMS, BANKTERM, BANKLDGR, and BE3ORDER are stopped at both IMSs.
Entry ET:
/STOP LINE 4,5,6,7,8,9,10,11
Response ET:
DFS058I STOP COMMAND COMPLETED
Response RT:
DFS059I TERMINAL STOPPED
Explanation: Lines 4, 5, 6, 7, 8, 9, 10, and 11 and their associated physical terminals are stopped.
Entry ET:
/STOP LINE 4 8 900
Response ET:
DFS058I STOP COMMAND COMPLETED EXCEPT LINE 900
Response RT:
DFS059I TERMINAL STOPPED
Explanation: Lines 4 and 8 and their associated physical terminals are stopped. 900 is an invalid line number.
Entry ET:
/STOP LINE 4 PTERM 1, 2
Response ET:
DFS058I STOP COMMAND COMPLETED
Response RT:
DFS059I TERMINAL STOPPED
Explanation: Physical terminals 1 and 2 on line 4 are stopped.
Entry ET:
/STOP LTERM APPLE, TREE, FRUIT
Response ET:
DFS058I STOP COMMAND COMPLETED
Response RT:
DFS059I TERMINAL STOPPED
Explanation: Logical terminals APPLE, TREE, and FRUIT are stopped.
Entry ET:
/STOP MSNAME BOSTON
Response ET:
DFS058I STOP COMMAND COMPLETED
Explanation: The logical link path associated with the name BOSTON is stopped.
Entry ET:
/STOP NODE HARRY
Response ET:
DFS058I STOP COMMAND COMPLETED
Explanation: The physical terminal associated with node HARRY is disconnected (/CLSDST) and further logons are prevented.
Entry ET:
/STO OTMA
Response ET:
DFS2361I 14:02:05 XCF GROUP CLOSED SUCCESSFULLY. SYS3 DFS058I 14:02:06 STOP COMMAND COMPLETED SYS3 DFS996I *IMS READY* SYS3
Entry ET:
/STOP OLDS 09
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS2500I DATASET DFSOLP09 SUCCESSFULLY DEALLOCATED DFS3257I OLDS DEALLOCATED ON DFSOLP09
Explanation: The subject OLDS, DFSOLP09 (DFSOLS09), will be stopped.
Entry ET:
/STOP PROGRAM APPLETRE
Response ET:
DFS058I STOP COMMAND COMPLETED
Explanation: Application program APPLETRE is stopped.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 1, 2 1 BMP BMP BMP BMP255 3 IFPN FPM NO MSG. DDLTJN26 DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/142004*
Explanation: Fast Path message-driven region 3 currently has no messages to process.
Entry ET:
/STOP REG 3
Response ET:
DFS058I STOP COMMAND IN PROGRESS
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE DBRC1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-In - 0 ACTIV-OUT - 0 *89041/142102*
Explanation: Fast Path region 3 has been stopped. If region 3 had been processing a message, IMS would have terminated the region on completion of the transaction.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/142102*
Entry ET:
/STOP REG 1
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS0557I STOP REGION ID NOT VALID- REGION 0001 IS BMP.
Explanation: /STOP REGION (with no keywords) is not valid for batch regions.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 1, 2 1 BMP BMP BMP BMP255 3 FPU FPU IFP DBF#FPU0 DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/142453*
Entry ET:
/STOP REG 3
Response ET:
DFS058I STOP COMMAND IN PROGRESS
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-In - 0 ACTIV-OUT - 0 *89041/142758*
Explanation: Fast Path utility region 3 has been stopped. The Fast Path utility DBF#FPU0 was terminated at the next system checkpoint.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE SYS3 VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/142758*
Explanation: Transaction TXCDRN24 in region 2 is looping or in a wait state.
Entry ET:
/STOP REG 2 ABDUMP TXCDRN24
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS555I TRAN TXCDRN24 ABEND S000,U0474 SYS ID 220 MSG IN PROGRESS
Explanation: The application program has been terminated with a U0474 ABEND. This abend indicates termination in response to a user request (/STOP REGION ABDUMP).
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP WAITING 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/143420*
Explanation: The application has been terminated but the region remains active.
Entry ET:
/DISPLAY PROG DDLTRN24
Response ET:
PROGRAM TRAN TYPE DDLTRN24 TXCDRN24 TP *90340/143749*
Explanation: The program has not been stopped.
Entry ET:
/DISPLAY TRANSACTION TXCDRN24
Response ET:
TRAN CLS ENQCT QCT LCT PLCT CP NP LP SEGSZ SEGNO PARLM RC TXCDRN24 2 1 0 65535 65535 1 1 1 0 0 0 0 PSBNAME: DDLTRN24 STATUS: STOP *90340/143802*
Explanation: The transaction has been stopped.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP WAITING 1, 2 1 BMP BMP BMP BMP255 3 FPU FPU IFP DBP#FPU0 DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/144248*
Entry ET:
/STOP REG 3 ABDUMP
Response ET:
DFS058I STOP COMMAND IN PROGRESS
Explanation: A transaction code is not entered when terminating a Fast Path utility with a /STOP REGION ABDUMP command.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 WAIT-INPUT 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINE ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/150141*
Explanation: Message processing program DDLTRN24 is waiting for an input message.
Entry ET:
/STOP REGION 2 TRANSACTION TXCDRN24
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS0569I PSTOP OR STOP COMPLETE FOR REGION0002 TRAN TXCDRN24.
Explanation: A QC status code was returned to the WFI application program DDLTRN24.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP WAITING 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-In - 0 ACTIV-OUT - 0 *89041/150206*
Explanation: The WFI application has been terminated but the region is still active.
Entry ET:
/DISPLAY TRANSACTION TXCDRN24
Response ET:
TRAN CLS ENQCT QCT LCT PLCT CP NP LP SEGSZ SEGNO PARLM RC TXCDRN24 2 4 0 65535 65535 1 1 1 0 0 0 0 PSBNAME: DDLTRN24 *90340/150219*
Explanation: The transaction is not stopped.
Entry ET:
/DISPLAY A
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS 2 MPP TP TXCDRN24 DDLTRN24 WAIT-INPUT 1, 2 1 BMP BMP BMP BMP255 FPRGN FP NONE DBR1CT13 DBRC VTAM ACB CLOSED LINE ACTIVE-IN - 1 ACTIV-OUT - 0 NODE ACTIVE-IN - 0 ACTIV-OUT - 0 LINK ACTIVE-IN - 0 ACTIV-OUT - 0 *89041/150813*
Entry ET:
/STOP REGION 2 TRANSACTION TRAN255
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS0558I TRAN TRAN255 NOT SCHEDULED
Explanation: TRAN255 is a valid transaction for the IMS system but it is not currently scheduled in region 2. If TRAN255 had not been a valid transaction for the IMS system, only message DFS230I (TRAN SPECIFIED WITH ABDUMP OR TRAN KEYWORD IS NOT VALID) would have been issued.
Entry ET:
D A,L
Response ET:
JOBS M/S TS USERS SYSAS INITS ACTIVE/MAX VTAM OAS 00001 00010 00001 00019 00020 00001/00020 00000 LLA LLA LLA NSW S VLF VLF VLF NSW S JES2 JES2 IEFPROC NSW S RMF RMF IEFPROC NSW S IMSVTAM IMSVTAM IEFPROC NSW S TSO TSO STEP1 NSW S CQS CQS IEFPROC NSW S IMSECTA9 IMSECTA9 IEFPROC NSW S DLIECTA9 DLIECTA9 DLISAS NSW S DBRECTA9 DBRECTA9 DBRC NSW S MPP610C MPP MPP NSW J USRT001 OWT
Explanation: MPP610C is an IMS message processing region.
Entry ET:
/STOP REGION JOBNAME MPP610C
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS552I MESSAGE REGION MPP610C STOPPED ID=00001 TIME=1616 SYSX SMF000I MPP610C MPP DFSRRC00 0000 $HASP395 MPP610C ENDED
Entry ET:
/STOP SB
Response ET:
DFS058 STOP COMMAND COMPLETED
Entry ET:
/DISPLAY POOL DBAS
Response ET:
SEQUENTIAL BUFFERING: STATUS = STOPPED MAX N.A. FREE N.A. CURR 0K HIGH 320K DATABASE BUFFER POOL: SIZE 67584 REQ1 0 REQ2 0 READ 0 BISAM 0 WRITES 0 KEYC 0 LCYL 0 PURG 0 OWNRR 0 ERRORS 00/00 DATABASE BUFFER POOL: BSIZE 12288 RRBA 0 RKEY 0 BFALT 0 NREC 0 SYN PTS 0 NMBUFS 29 VRDS 0 FOUND 0 VWTS 0 ERRORS 00/00 DATABASE BUFFER POOL: BSIZE 356352 RRBA 0 RKEY 0 BFALT 0 NREC 0 SYN PTS 0 NMBUFS 29 VRDS 0 FOUND 0 VWTS 0 ERRORS 00/00 *90253/104547*
Explanation: Sequential buffering is stopped.
Entry ET:
/STOP SUBSYS ALL
Response ET:
DFS058I STOP COMMAND IN PROGRESS
Explanation: IMS has initiated the termination of the connection. When all dependent regions have terminated their connections, IMS will complete the termination. It is likely that an external subsystem message indicating connection termination will be received at this time.
Entry ET:
/STOP SUBSYS XXX1 XXX3
Response ET:
DFS058I STOP COMMAND IN PROGRESS
Explanation: IMS has initiated the termination of the connection. When all dependent regions have terminated their connections, IMS will complete the termination. It is likely that an external subsystem message indicating connection termination will be received at this time
Entry ET:
/DISPLAY A THREAD
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS BATCHREG BMP NONE FPRGN FP NONE 2 CICS1A DBT IEFPROC BMP255 ACTIVE 3 CICS1A DBT IEFPROC PLVAPZ12 ACTIVE 1 CICS1A DBT IEPROC AVAILABLE DBRCHTA1 DBRC DLICHTA1 DLS *00082/142907*
Entry ET:
/STOP THREAD 2
Response ET:
DFS058I STOP COMMAND IN PROGRESS DFS0556I COMMAND REJECTED; DBCTL THREAD IS ACTIVE
Entry ET:
/DISPLAY A THREAD
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS BATCHREG BMP NONE FPRGN FP NONE 2 CICS1A DBT IEFPROC BMP255 ACTIVE 3 CICS1A DBT IEFPROC PLVAPZ12 ACTIVE 1 CICS1A DBT IEFPROC AVAILABLE DBRCHTA1 DBRC DLICHTA1 DLS *00082/143027*
Entry ET:
/STOP THREAD 1
Response ET:
DFS058I STOP COMMAND IN PROGRESS
Entry ET:
/DISPLAY A THREAD
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS BATCHREG BMP NONE FPRGN FP NONE 2 CICS1A DBT IEFPROC BMP255 ACTIVE 3 CICS1A DBT IEFPROC PLVAPZ12 ACTIVE DBRCHTA1 DBRC DLICHTA1 DLS *00082/143055*
Entry ET:
/DISPLAY A THREAD
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS BATCHREG BMP NONE FPRGN FP NONE 2 CICS1A DBT IEFPROC BMP255 ACTIVE 3 CICS1A DBT IEFPROC PLVAPZ12 ACTIVE DBRCHTA1 DBRC DLICHTA1 DLS *00082/144731*
Entry ET:
/STOP THREAD 2 ABDUMP
Response ET:
/DFS058I STOP COMMAND IN PROGRESS
Response ET:
DFS554A CICS1A 00002 IEFPROC BMP255 (3) 000,0474 20 /082 14:49:11 RTKN= CICS1 B3C81CB789F4BE83
Entry ET:
/DISPALY A THREAD
Response ET:
REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS CLASS BATCHREG BMP NONE FPRGN FP NONE 3 CICS1A DBT IEFPROC PLVAPZ12 ACTIVE DBRCHTA1 DBRC DLICHTA1 DLS *00082/145038*
Entry ET:
/STO TMEMBER CLIENT1 TPIPE TPIPESY
Response ET:
DFS058I 15:38:03 STOP COMMAND COMPLETED SYS3 DFS996I *IMS READY* SYS3
Entry ET:
/STOP TRANSACTION ALL CLASS 6
Response ET:
DFS058I STOP COMMAND COMPLETED
Explanation: All transactions associated with class 6 will be marked as stopped and all class 6 transactions are no longer available for scheduling. All message processing regions currently processing class 6 transactions are allowed to run until the processing limit count is reached or the input queue contains no more messages.
Entry ET:
/STOP TRANSACTION PIT, SEED
Response ET:
DFS058I STOP COMMAND COMPLETED
Explanation: Transaction codes PIT and SEED are stopped.
Entry ET:
/DISPLAY USER IMS*
Response ET:
USER ENQCT DEQCT QCT SYS3 IMSUS06 0 0 0 ALLOC(DTSLU602) IMSUS04 0 0 0 ALLOC(DTSLU603) IMSUS03 0 0 0 ALLOC(DTSLU601) IMSUS02 0 0 0 ALLOC(DTSLU202) IMSUS01 0 0 0 ALLOC(DTSLU201) IMSUS09 N/A N/A N/A ALLOC(ENDS02 ) STATIC IMSUS08 N/A N/A N/A ALLOC(ENDS01 ) STATIC IMSUS11 N/A N/A N/A ALLOC(ENDS03 ) STATIC IMSUS10 N/A N/A N/A ALLOC(OMSSLU2A) STATIC *91091/111454*
Entry ET:
/STOP USER IMSUS01 IMSUS02
Response ET:
DFS058I 11:16:24 STOP COMMAND COMPLETED
Entry ET:
/STOP USER HELLO%
Response ET:
DFS3633 11:18:25 GENERIC PARAMETER RESOURCES NOT FOUND, NO ACTION TAKEN
Entry ET:
/DISPLAY USER IMSUS01 IMSUS02
Response ET:
USER ENQCT DEQCT QCT IMSUS01 0 0 0 STOPPED IMSUS02 0 0 0 STOPPED *91091/111727*