/START commands
The /START commands make IMS™ resources available for reference and use.
/START also checks the validity of
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 /START command
processes the rest of the parameters. For example,
/START LINE 4 6 200
DFS058 START COMMAND COMPLETED EXCEPT LINE 200When a resource becomes available, the system parameters used for this initialization of IMS are displayed in message DFS1929I. The system parameters are also written to the job log.
These commands can be issued to an IMSplex using the Batch SPOC utility.
- /START APPC command
Use the /START APPC command to instruct IMS to activate the connection to APPC/z/OS and to start accepting transaction schedule requests from APPC/z/OS. - /START AREA command
Use the /START AREA command to specify the specific areas of DEDBs to be allocated. For z/OS®, you can use the /START AREA command to reallocate DEDB areas. - /START AUTOARCH command
Use the /START AUTOARCH command to set the value to change the automatic archiving option selected at system initialization or to set the value to start automatic archiving after a previous /STOP AUTOARCH command. - /START CLASS command
Use the /START CLASS command to specify transaction class, allowing scheduling of application programs to begin. - /START DATAGRP command
Use the /START DATAGRP command to specify groups of DL/I databases and Fast Path DEDBs to be allocated. - /START DB command
Use the /START DB command to specify the DBD name. The /START DB command permits access from transactions that read or update databases. - /START DC command
Use the /START DC command to open the VTAM® ACBs (if MNPS for XRF is used, then both the MNPS and APPLID ACBs are opened) if they are not already open, to enable logons to IMS, and to enable optional transaction manager functions such as IMS generic resource support and IMS persistent sessions support for RNR. - /START DESC command
Use the /START DESC command to define the LU62 descriptors from DFS62xxx PROCLIB member to IMS. - /START ISOLOG command
The /START ISOLOG command indicates that the RSR tracking subsystem is to initiate a request for isolated log data from the isolated log sender at the active site. - /START LINE command
The /START LINE command makes communication lines that are idle and in a stopped or process stopped state available for use. It also terminates any conversations that are active on the line. - /START LTERM command
Use the /START LTERM command to specify the logical terminals to be started and to reset the QLOCK 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.) /START LTERM is rejected for remote logical terminals. - /START LUNAME command
Use the START LUNAME command to specify the LU name that is to be started. - /START MADSIOT command
Use the /START MADSIOT command to specify the MADS I/O timing function. - /START MSNAME command
Use the /START MSNAME command to specify the logical link path that is to be started. The MSNAME keyword can be generic. - /START NODE command
Use the /START NODE command to allow IMS to accept logons from, or initiate logons to, terminals attached to VTAM without actually initiating a session with the terminal. When a stopped node is started by using the /START NODE command, the terminal can log on to IMS or IMS can initiate a session with the terminal by using the /OPNDST NODE command. - /START OLDS command
The /START OLDS command indicates that either a previously stopped OLDS is to be started or that IMS is to add a new OLDS log data set. - /START OTMA command
Use the /START OTMA command to cause IMS to join the z/OS cross-system coupling facility (XCF) group for the IMS Open Transaction Manager Access (OTMA). - /START PGM command
Use the /START PGM command to specify the application program that is to be started. - /START REGION command
Use the /START REGION command to specify the set of message processing region JCL to be passed to z/OS. If no member name is specified, the default member name is used - /START RTC command
Use the /START RTC command to specify the Fast Path routing codes to be activated and to allow transactions associated with the routing codes to be processed. - /START SB command
Use the /START SB command to dynamically allow sequential buffering. This command does not affect sequential buffering applications scheduled before this command was issued. - /START SERVGRP command
Use the /START SERVGRP command to start communications between the entering service group and the service group at the other site in an Remote Site Recovery (RSR) complex. - /START SLDSREAD command
The /START SLDSREAD command indicates whether IMS is enabled to retrieve records from both a system log data set (SLDS) and OLDS or OLDS only. The default is that SLDSREAD is enabled. - /START SUBSYS command
Use the /START SUBSYS command to specify the external subsystem to which IMS is to connect. - /START SURV command
Use the /START SURV command in an XRF environment to start the operation of the IMS surveillance function. - /START THREAD command
Use the /START THREAD command to specify the set of message processing region JCL to be passed to z/OS. If no member name is specified, the default member name is used. - /START TMEM command
Use the /START TMEM command to cause IMS to send an Open Transaction Manager Access (OTMA) command to OTMA clients to request that input resume for the specified transaction membername. IMS then resumes sending output to the OTMA client. - /START TRAN command
Use the /START TRAN command to specify the transactions to be started. - /START TRKARCH command
Use the /START TRKARCH command to indicate that the RSR tracking subsystem is to initiate a request to start the automatic archiving of the tracking log data sets. - /START USER command
Without the NODE keyword, USER specifies the ISC user or the dynamic user to start. The USER parameter can be generic where the generic parameter specifies users that already exist. - /START VGR command
The /START VGR command causes the IMS subsystem to join a VTAM generic resource group. The command is rejected if the VTAM ACB is closed (usually the result of a /STOP DC command). - /START WADS command
The /START WADS command indicates that either a previously stopped WADS is to be started or that IMS is to add a new WADS to the pool of available WADSs. - /START XRCTRACK command
The /START XRCTRACK command results in calls to the log router to initiate or terminate XRC tracking. It is only valid on a tracking IMS system.
Parent topic: IMS commands