/START Command: APPC through MADSIOT >>-+-/START-+---------------------------------------------------> '-/STA---' >--+-APPC--------------------------------------------+--------->< | .----------. | | V | .-LOCAL--. | +-AREA--+---areaname-+--+--------+-+--------------+ | | '-GLOBAL-' | | | | .-LOCAL-. | | | '-ALL--+-------+-----------' | +-AUTOARCH--+-------+-----------------------------+ | '-#olds-' | | .------. | | V | | +-CLASS--+---cls#-+-+-----------------------------+ | '-ALL------' | | .--------. | | V | .-LOCAL-. | +-DB--+---dbname-+--+-+-------+--| A |-+--| C |-+-+ | | '-GLOBAL-----------' | | | | .-LOCAL-. | | | '-ALL--+-------+--| A |--| B |------------' | +-DATAGRP--datagroupname--+-------+--| A |--| B |-+ | '-LOCAL-' | +-DESC--proclibmember-----------------------------+ +-DC----------------------------------------------+ +-ISOLOG------------------------------------------+ | .-------. | | 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-----------------------------------------' A: |--+----------------+-------------------------------------------| '-ACCESS=-+-RO-+-' +-RD-+ +-UP-+ '-EX-' B: .-NODBALLOC-. |--+-DBALLOC---+------------------------------------------------|
C: .-DBALLOC---. .-NOOPEN-. |--+-----------+--+-NODBALLOC-+--+--------+---------------------| '-NOBACKOUT-' '-OPEN---'
/START Command: MSNAME through TMEM >>-+-/START-+---------------------------------------------------> '-/STA---' .-------------. V | >--+-MSNAME--+---+-msname--+-+-+-----------------------------+->< | | '-msname*-' | | | '-ALL-------------' | | .---------------. | | V | | +-NODE--+---+-nodename--+-+----------------+--------------+ | | '-nodename*-' | | | | .----------. | | | | V | | | | +-nodename--USER--+---username-+-+-+ | | | '-ALL----------' | | | '-ALL------------------------------' | +-OLDS--olds#---------------------------------------------+ +-OTMA----------------------------------------------------+ | .---------. | | V | | +-PGM--+---pgmname-+-+------------------------------------+ | '-ALL---------' | | .----------------. | | V | | +-REGION--+---+------------+-+--+-------+---------------+-+ | | '-membername-' '-LOCAL-' | | | | .---------. | | | | V | .-LOCAL-. | | | '-membername--JOBNAME----jobname-+--+-------+-' | | .---------. | | V | | +-RTC--+---rtcname-+-+------------------------------------+ | '-ALL---------' | +-SB------------------------------------------------------+ +-SERVGRP-------------------------------------------------+ +-SLDSREAD------------------------------------------------+ | .------------. | | V | | +-SUBSYS--+---subsysname-+-+------------------------------+ | +-ALL------------+ | | '-SSM--ssmname---' | | .-ALL-. | +-SURV--+-----+-------------------------------------------+ | +-LNK-+ | | +-LOG-+ | | '-RDS-' | | .----------------. | | V | | +-THREAD----+------------+-+------------------------------+ | '-membername-' | '-TMEM--tmembername--+----------------------+-------------' '-TPIPE--+-tpipename-+-' '-ALL-------'
/START Command: TRAN through XRCTRACK .---------------. V | >>-+-/START-+--+-TRAN--+---+-tranname--+-+------------+--+----->< '-/STA---' | | '-tranname*-' | | | '-ALL--+---------------------+-' | | | .------. | | | | V | | | | '-CLASS--+---cls#-+-+-' | | '-ALL------' | +-TRKARCH---------------------------------+ | .---------------. | | V | | +-USER--+---+-username--+-+-+-------------+ | | '-username*-' | | | '-ALL---------------' | +-VGR--+--------------------------------+-+ | '-GRSNAME--generic_resource_name-' | +-WADS--wads#-----------------------------+ '-XRCTRACK--------------------------------'
Table 154 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.
Command / Keywords | DB/DC | DBCTL | DCCTL |
---|---|---|---|
/START | X | X | X |
ACCESS | X | X | |
APPC | X | X | |
AREA | X | X | |
AUTOARCH | X | X | X |
CLASS | X | X | |
DB | X | X | |
DATAGRP | X | X | |
DBALLOC | X | X | |
DC | X | X | |
DESC | X | X | |
GLOBAL | X | X | |
GRSNAME | X | X | |
INPUT | X | X | |
ISOLOG | X | X | X |
JOBNAME | X | X | X |
LINE | X | X | |
LOCAL | X | X | |
LTERM | X | X | |
LU | X | X | |
MADSIOT | X | X | |
MSNAME | X | X | |
NOBACKOUT | X | X | |
NODBALLOC | X | X | |
NODE | X | X | |
NOOPEN | X | X | |
OLDS | X | X | X |
OPEN | 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 |
SSM | 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 | |
TRKARCH | X | X | X |
USER | X | X | |
VGR | X | X | |
WADS | X | X | X |
XRCTRACK | X | X | X |
The /START command makes IMS resources available for reference and use.
The /START command can be used on HALDBs. For more information see High Availability Large Database Commands
/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 200
signifies parameter value 200 is not a valid line number.
When 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.
The /START APPC command sets the desired status to ENABLED. The current status is initially set to STARTING. When APPC/z/OS responds to the start request, the status changes to either ENABLED or FAILED.
For areas on an RSR tracking subsystem, /START AREA is used to resume tracking for those areas that were stopped by a previous /DBRECOVERY command or by errors found during tracking subsystem processing. /START AREA also starts online forward recovery (OFR) for those areas that are not current with mainline tracking.
For virtual storage option (VSO) areas that have been defined with the PREOPEN option, /START AREA causes the areas to be preopened. If the VSO area is defined with the PRELOAD option, /START AREA causes the area to be opened and loaded into the z/OS data space.
Restriction: This command only applies to the IMS subsystem on which it is entered; it does not preload or preopen areas on other IMS subsystems in the sysplex that share the area.
The /START AREA command has no effect on VSO areas that are in virtual storage when the command is issued.
The output of the /START 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: DFS0011I, DFS140I, DFS0488I, DFS0666I, DFS1407I, DFS2980E, DFS2981E, DFS3320I, DFS3325I, DFS3342I, DFS3720I, DFS3824I
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 is processed only by the command master IMS. |The command master IMS 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. All other non-master IMSs ignore the /START command with the GLOBAL keyword.
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 155:
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. |
LOCAL is the default.
/START AREA ALL causes message DFS0488 to be issued for every area that is not started successfully, but you do not see a DFS0488 message for every area that does start successfully. You do see a final DFS0488 message which indicates the end of command processing.
/START AUTOARCH will not be carried over a warm start if a checkpoint has occurred after the command has been successfully completed, and before a warm start has been issued.
For a DEDB, the /START DATABASE command also causes any unloaded randomizer, specified in the DBD source, to be reloaded.
When the name that is specified is for a partition, the action taken to allocate data sets varies. The action varies depending on the status of the master database and whether the DMB for the master database is already loaded. If a /DBRECOVERY command has not been issued against the master database, the DMB is already loaded in the following situations:
|PHDAM or PHIDAM partitions that had the /DBRECOVERY command issued against them, cannot be allocated with the /START DATABASE DBALLOC command. However, if the partition databases have EEQEs, |or the OPEN keyword is used with the /START DATABASE command, or the databases were previously authorized but |not allocated, the partitions can be allocated. If you do not use |the OPEN keyword, the PSINDEX partition is allocated and the PHDAM |and PHIDAM partitions are not allocated until they are authorized.
When a /START DATABASE command is issued for all transactions whose processing program has access to a successfully started database, the USTOPPED attribute will be reset and any messages on the suspend queue for that transaction will be transferred to the normal queue.
If one or more of the named databases requires backout or recovery, and the database is registered in DBRC, the database requiring backout or recovery is dropped from the command and the remainder of the databases continue processing. If the database is not registered in DBRC, specify the NOBACKOUT keyword to inform IMS that it does not have to attempt to execute the failed backout again.
To start a HIDAM database, both the index and the data area DBD names must be specified. If a backout failure occurred for this database, the /START command causes the backout to be attempted again.
If the database specified in the command is being used by a batch message processing region, an error message is returned to the master terminal, and the command is ignored for the database named in the message. Processing continues for the other databases specified in the command. The master terminal operator must wait until the batch message processing concludes before reentering the command.
For databases on an RSR tracking subsystem, /START DATABASE is used to resume tracking for those databases that were stopped by a tracking subsystem processing. /START DATABASE also starts online forward recovery (OFR) for those databases that are not current with mainline tracking.
/START DATABASE ALL causes message DFS0488I to be issued. All databases that were defined at sysgen will be started if possible.
The output of the /START 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: DFS030I, DFS132, DFS160, DFS216, DFS0402I, DFS0488I, DFS0740I, DFS1407, DFS2026, DFS3317I, DFS3318I, DFS3320I, DFS3325I, DFS3465I, DFS3466I
Fast Path Database messages: DFS140I, DFS666, DFS3062
For the results of issuing this command on a shared secondary index, see Shared Secondary Index Database Commands
Changing the access intent of a database with the /START DB ACCESS= command causes any VSO areas of the database to be removed from virtual storage. Because the access intent of a DEDB cannot be changed while any of its areas are authorized to an IMS subsystem, IMS closes any open areas before processing the command. If a VSO area is closed as a result of the command, it is also removed from the data space.
The /START AREA command must be used to reactivate the VSO options (VSO and PREOPEN) and PRELOAD option for the area. If an area is opened as a result of an access request rather than by the /START AREA command, it is opened as a non-VSO area.
Non-VSO areas with the PREOPEN option are closed as a result of the /START DB ACCESS= command. These areas are reopened either at the next access request for the area or by the /START AREA command.
The GLOBAL and ACCESS keywords are mutually exclusive. The /START command is rejected if both keywords are specified.
The meanings of the ACCESS parameter values are:
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 156:
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. |
LOCAL is the default.
If the database is registered in DBRC and is using share control, then DBRC is informed when batch backout is successfully executed, and the failing backout will not be attempted again when the /START command is issued.
If the database is registered in DBRC and is using recovery control, DBRC is not informed when batch backout is successfully executed. You must specify the NOBACKOUT keyword to inform IMS that it does not have to attempt to execute the failed backout again.
NOBACKOUT is not valid with the ALL parameter.
Restrictions: The OPEN |parameter is not supported: |
|Related Reading: See Group Parameters for more information on defining data groups.
For databases and areas on an RSR tracking subsystem, /START DATAGROUP is used to resume tracking for those areas that were stopped by a previous /DBRECOVERY command or by errors found during tracking subsystem processing. /START DATAGROUP also starts online forward recovery (OFR) for those databases and areas that are not current with mainline tracking.
After processing for a /START DATAGROUP completes, a DFS0488 message is issued indicating the end of processing. A DFS0488 message is also issued for every database or area that does not start successfully.
If the datagroup contains both full function and Fast Path databases, a DFS0488 message might be issued indicating the /START DATAGROUP command completed successfully before any messages are issued that indicate a Fast Path area did not start successfully. This situation is due to the asynchronous processing of Fast Path databases.
For virtual storage option (VSO) areas that have been defined with the PREOPEN option, /START AREA causes the areas to be preopened. If the VSO area is defined with the PRELOAD option, /START AREA causes the area to be opened and loaded into the z/OS data space.
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.
Changing the access intent for a DEDB is allowed only when no PSBs are scheduled that access any areas in the DEDB. You might have to stop PSBs and regions that have wait-for-input (WFI) transactions scheduled before you can change a DEDB's access intent.
Changing the access intent of a database with the /START DB ACCESS= command causes any VSO areas of the database to be removed from virtual storage. Because the access intent of a DEDB cannot be changed while any of its areas are authorized to an IMS subsystem, IMS closes any open areas before processing the command. If a VSO area is closed as a result of the command, it is also removed from the data space.
The /START AREA command must be used to reactivate the VSO options (VSO and PREOPEN) and PRELOAD option for the area. If an area is opened as a result of an access request rather than by the /START AREA command, it is opened as a non-VSO area.
Non-VSO areas with the PREOPEN option are closed as a result of the /START DB ACCESS= command. These areas are reopened either at the next access request for the area or by the /START AREA command.
The GLOBAL and ACCESS keywords are mutually exclusive. The /START command is rejected if both keywords are specified.
The meanings of the ACCESS parameter values are:
The only programs which can use the database on this subsystem are those which have a PCB processing option of GO (PROCOPT=GO). Programs which access the data using the GO processing option might see uncommitted data, since a sharing IMS subsystem could be updating the database, which is opened for input only.
Programs with update intent can be scheduled, but cannot update the database. ACCESS=RD differs from ACCESS=RO in that the data is read with integrity (locking is performed) and all programs can access the data, not just those with a processing option of GO. The database is opened for read only.
This exclusive access is guaranteed only when the database is registered to DBRC.
LOCAL is the default.
If the /START DC command is issued on an XRF alternate system that is using MNPS, |the command will only open the APPLID ACB. The MNPS ACB is not opened |until XRF takeover processing.
Successful completion of syntax checking of the /START ISOLOG command results in the DFS058 START COMMAND COMPLETED message, although processing of the command continues asynchronously.
If the line must be enabled again, /START LINE must be entered prior to any /START LINE PTERM command.
The /START LINE PTERM command makes one or more physical terminals available for use. The physical terminals are removed from response mode, test mode, looptest mode, MFSTEST mode, preset destination mode, or exclusive mode, and resets terminals in signon status. If IMS encounters a stopped and idle line when processing /START LINE PTERM, it restarts the line. Any inoperable components are marked as operable.
To activate I/O operations for a LINE, LINE PTERM, or NODE without altering the status of the associated/specified terminals, use /RSTART instead of /START.
If an error is detected on parameters that are independent of one another, only the invalid parameters are indicated as being in error and processing continues for the rest of the parameters. This happens for /START LINE if:
/START LINE no longer resets preset mode, test mode, and response mode since these statuses are no longer significant and therefore are not kept after a /START LINE or restart command.
The LTERM keyword is only effective for existing LTERMs.
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/START LTERM command allows messages to be queued to the LTERM from anywhere in the IMSplex and the change is reflected both in Resource Manager and in the local IMS system.
Specifying the keyword INPUT starts an luname for any input and synchronous outbound activities. Specifying the parameter ALL with the keyword INPUT causes all future LU 6.2 inbound and synchronous output activities to be started as well.
Specifying the keyword OUTPUT starts an luname for asynchronous outbound activities. Specifying the parameter ALL with the keyword OUTPUT causes all future LU 6.2 outbound asynchronous activities to be started as well.
Specifying neither INPUT nor OUTPUT is the same as specifying both INPUT and OUTPUT. The LU name is started for any input and both synchronous and asynchronous outbound activities. Specifying the parameter ALL in this case also causes the start of all future LU 6.2 inbound activities, outbound synchronous, and asynchronous 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 the network-qualified LU names whose LU name matches the LU name specified are also started.
/START LUNAME TPNAME starts a particular tpname of an luname. The keyword OUTPUT is the default for this command.
If the specified resource does not exist, a structure is created to retain the status.
The purpose of this command is to enable 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 enabled, the command will be ignored. If MADS I/O Timing function is not enabled and all sharing partners successfully connect to MADS I/O Timing list structure on the coupling facility, the command will complete successfully; if any sharing partners fails to connect to MASD I/O Timing list structure, the command will fail.
The output of the /STA 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, DFS0007I, DFS1270I, DFS1727I, DFS1552A, DFS1728E
The /START NODE command is only effective for existing nodes.
If an ETO logon terminal is stopped, use the /OPNDST NODE USER command to start it, not the /START NODE command.
If Fast Path is active for a specified physical terminal or node, /START LINE and /START NODE cannot reset terminal response mode. The /DEQUEUE command must be entered to discard Fast Path output before using /START.
The /START NODE nodename USER username command applies to ISC sessions only, and it is used to start a half-session allocated to USER username for NODE nodename. The USER keyword when used with the NODE keyword affects the specified half-session. When the USER keyword is omitted, all half-sessions of the specified node are affected.
The NODE parameter can be generic if the USER keyword is not present. The generic parameter specifies nodes that already exist.
/START NODE no longer resets response mode, test mode, and preset mode, since these statuses are no longer significant and therefore no longer carried across logon or restart. MFSTEST mode (at the node level) and exclusive mode are still reset.
If global resource information is kept in Resource Manager, the /START NODE command allows a node to logon to any IMS in the IMSplex and resets MFSTEST mode and exclusive mode. If the node no longer has significant status, it is deleted from Resource Manager.
When using /START OLDS, an OLDS must be defined in the DFSMDA macro, even if it is allocated in JCL.
/START OTMA command processing is as follows:
/START PROGRAM does not start a CPI Communications driven transaction program.
IMS dependent regions of the same type (MPP, BMP, or IFP) can share a PROCLIB member containing the startup JCL for the type of region. Use the JOBNAME or LOCAL keywords of the /START REGION command to allow IMS to set (or override) the IMS ID for the dependent region to match the IMS ID of the IMS that processes the command.
Restriction: The JCL for the region to be started must include the IMSID= execution parameter.
Use the JOBNAME keyword to override the job name on the JOB statement of the default or specified JCL member for a dependent region.
If you specify the LOCAL keyword, IMS overrides the symbolic IMSID parameter in the JCL of the default or specified member. LOCAL is the default if you specify the JOBNAME keyword.
When the LOCAL or JOBNAME keywords are specified on the /START REGION command, the PROCLIB member must be a job that runs a procedure to start the dependent region. The procedure cannot be an instream procedure. For example, suppose that the /START REGION command is entered in one of the following formats:
/START REGION member_name LOCAL /START REGION member_name JOBNAME job_name /START REGION member_name JOBNAME job_name LOCAL
In these instances, member_name is a job that runs a procedure to start the dependent region and has the following format:
//job_name JOB ... (parameters)... // EXEC proc_name, // IMSID=xxxx
|The operator can start more dependent regions than |were specified in the IMS system definition or the EXEC parameter, |up to 999. A request to start more regions than the system-definition |value (but less than or equal to 999) might be rejected if resources |are not available.
The /START REGION command is not mirrored on the XRF alternate subsystem. You must enter this command on the alternate subsystem if you want it to affect the alternate subsystem.
The /START SERVGRP command is not normally needed for an active subsystem, since the logger normally attempts to identify to transport manager at each OLDS switch to establish connections with the other subsystem. However, the operator may want to trigger this process between OLDS switches; for instance if a network outage between the active and tracking sites has been repaired and the operator does not want to wait until the next OLDS switch to re-establish communications.
Successful completion of the syntax checking of the /START SERVGRP command results in the DFS058 START COMMAND COMPLETED message, although processing of the command continues asynchronously.
The syntax and usage of the SSM keyword are the same as the SSM=EXEC parameter that can be specified on the IMS startup JCL. The SSM keyword is followed by a 1 to 4 character identifier. IMS concatenates the SSM identifier to the IMSID to create an SSM PROCLIB member name. The SSM Proclib member is then used for external subsystem processing.
The SSM keyword is not valid if either of the following conditions apply:
The /START SUBSYS ALL command connects IMS to all external subsystems. Also, the SSM keyword can be used with the /START SUBSYS command.
If the subsystem connection was abnormally terminated, IMS puts the connection in a stopped state. In this instance, the /START command must be used to reestablish the connection.
The surveillance function is generally started during IMS system definition by using the /START SURVEILLANCE control statement. ALL is the default.
The /START THREAD command is used only for DEDB utility regions. BMP regions are started by JCL. CCTL threads are started automatically at connection: first to the MINTHREAD value, and later (on demand) to MAXTHREAD value.
Restriction: If a transaction pipe has a resynchronization pending status, IMS does not start the transaction pipe.
The /START TRANSACTION ALL CLASS cls# command causes all transactions associated with the specified class to be started.
If a transaction that has messages on the suspend queue is started, the suspend queue associated with the transaction will automatically be transferred to the normal queue.
The TRANSACTION keyword can be generic where the generic parameter specifies transactions that already exist.
Successful completion of the syntax checking of the /START TRKAUTOARCH command results in the DFS058I START COMMAND COMPLETED message, although processing of the command continues asynchronously.
/START USER applies only to users that are stopped and signed off. The /START USER command also terminates any active conversations before starting the user.
/START USER removes the user from MFSTEST mode and exclusive mode. If the USER structure is temporary and the status conditions that caused the creation of the structure have been reset, the temporary user is deleted at the next simple checkpoint.
For ISC users, the user is started and made available for allocation.
For dynamic users, the user is started and made available for signon.
/START USER no longer removes the user from response mode, test mode, and preset mode. MFSTEST mode can now be associated with the node and with the user. MFSTEST mode (at the user level) and exclusive mode are still reset. The other statuses are no longer significant and therefore not carried across signon or restart.
If global resource information is not kept in Resource Manager, the /START USER command allows a user to signon to the local IMS. If global resource information is kept in Resource Manager, the /START USER command allows a user to signon to any IMS in the IMSplex.
The GRSNAME keyword allows you to specify the generic resource name if the IMS subsystem does not have one. The IMS subsystem already has a generic resource name if it has the GRSNAME= keyword specified on its EXEC statement.
When using /START WADS, a WADS must be defined in the DFSMDA macro, even if it is allocated in JCL.
Entry ET:
/START AREA DB1AREA0 DB1AREA1
Response ET:
DFS058I START COMMAND IN PROGRESS DFS0488I START COMMAND COMPLETED. AREA=DB1AREA0 DFS0488I START COMMAND COMPLETED. AREA=DB1AREA1
Explanation: DEDB areas DB1AREA0 and DB1AREA1 are started.
Entry ET:
/START AUTOARCH 4
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: Automatic archiving will be initiated after 4 OLDS data sets are filled.
TSO SPOC input:
STA DB BANKATMS BANKTERM BANKLDGR BE3ORDER
TSO SPOC output:
SYS3 DFS0488I STA COMMAND COMPLETED. DBN= BANKATMS RC=04 SYS3 DFS0488I STA COMMAND COMPLETED. DBN= BANKTERM RC=04 SYS3 DFS0488I STA COMMAND COMPLETED. DBN= BANKLDGR RC=04 SYS3 DFS0488I STA COMMAND COMPLETED. DBN= BE3ORDER RC=08 IMS3 DFS0488I STA COMMAND COMPLETED. DBN= BANKATMS RC=04 IMS3 DFS0488I STA COMMAND COMPLETED. DBN= BANKTERM RC=04 IMS3 DFS0488I STA COMMAND COMPLETED. DBN= BANKLDGR RC=04 IMS3 DFS0488I STA COMMAND COMPLETED. DBN= BE3ORDER RC=08
OM API input:
CMD (STA 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 21:59:29.210362</statime> <stotime>2002.197 21:59:30.213238</stotime> <staseq>B7EFC01B367FAE02</staseq> <stoseq>B7EFC01C2B576D8F</stoseq> <rqsttkn1>USRT005 10145929</rqsttkn1> <rc>0200000C</rc> <rsn>00003008</rsn> </ctl> <cmderr> <mbr name="SYS3 "> <typ>IMS </typ> <styp>DBDC </styp> <rc>00000014</rc> <rsn>00005050</rsn> </mbr> <mbr name="IMS3 "> <typ>IMS </typ> <styp>DBDC </styp> <rc>00000014</rc> <rsn>00005050</rsn> </mbr> </cmderr> <cmd> <master>SYS3 </master> <userid>USRT005 </userid> <verb>STA </verb> <kwd>DB </kwd> <input>/STA DB BANKATMS BANKTERM BANKLDGR BE3ORDER </input> </cmd> <msgdata> <mbr name="SYS3 "> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BANKATMS RC=04</msg> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BANKTERM RC=04</msg> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BANKLDGR RC=04</msg> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BE3ORDER RC=08</msg> </mbr> <mbr name="IMS3 "> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BANKATMS RC=04</msg> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BANKTERM RC=04</msg> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BANKLDGR RC=04</msg> <msg>DFS0488I STA COMMAND COMPLETED. DBN= BE3ORDER RC=08</msg> </mbr> </msgdata> </imsout>
Explanation: The START DB 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 started at both IMSs.
Entry ET:
/START CLASS ALL
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: All classes of transactions are made available for scheduling into message processing regions.
Entry ET:
/START DATABASE TREEFARM
Response ET:
DFS058I (time stamp) START COMMAND IN PROGRESS DFS0488I START COMMAND COMPLETED. DBN=TREEFARM RC=0.
Explanation: Database TREEFARM is started.
Entry ET:
/START LINE 4 PTERM 1, 2
Response ET:
DFS058I START COMMAND COMPLETED
Response RT:
DFS059I TERMINAL STARTED
Explanation: Physical terminals 1 and 2 on line 4 are started.
Entry ET:
/START LINE 4,5,6,7,8,9,10,11
Response ET:
DFS058I START COMMAND COMPLETED
Response RT:
DFS059I TERMINAL STARTED
Explanation: Lines 4,5,6,7,8,9,10, and 11 are started.
Entry ET:
/START LINE 4 5 6 700
Response ET:
DFS058I START COMMAND COMPLETED EXCEPT LINE 5 700
Response RT:
DFS059I TERMINAL STARTED
Explanation: Lines 4 and 6 are started. The /DISPLAY LINE command can be used to determine why line 5 did not start successfully. (700 is an invalid line number.)
Entry ET:
/START LTERM APPLE, TREE, FRUIT
Response ET:
DFS058I START COMMAND COMPLETED
Response RT:
DFS059I TERMINAL STARTED
Explanation: Logical terminals APPLE, TREE, and FRUIT are started.
Entry ET:
/START MSNAME CHICAGO
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: A logical link path associated with the name CHICAGO is started.
Entry ET:
/START NODE HARRY
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: The physical terminal associated with the node HARRY is started.
Entry ET:
/STA OTMA
Response ET:
DFS2360I 14:02:53 XCF GROUP JOINED SUCCESSFULLY. SYS3 DFS058I 14:02:53 START COMMAND COMPLETED SYS3 DFS996I *IMS READY* SYS3
Entry ET:
/START OLDS 09
Response ET:
DFS058I START COMMAND IN PROGRESS
Explanation: OLDS data set DFSOLP09 (DFSOLS09) will be started for logging.
Entry ET:
/START PROGRAM ALL
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: All application programs are started.
Entry ET:
/START PROGRAM APPLETRE
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: Application program APPLETRE is started.
Entry ET:
/START REGION
Response ET:
DFS058I START COMMAND IN PROGRESS
Response ET:
DFS551I IFP|MESSAGE|BATCH REGION XXXXXXXX STARTED. ID=yy TIME=zzzz CLASSES=xxx,xxx,xxx,xxx
Explanation: One message region or batch region (ID=yy) is started at TIME=zzzz. The transactions associated with the classes listed in the response can now be scheduled.
Entry ET:
/START REGION IMSWT000
Response ET:
DFS058I START COMMAND IN PROGRESS
Explanation: The JCL stored as member IMSWT000 is used to start the spool SYSOUT utility for the data sets associated with the spool line corresponding to the IMSWT000 procedure.
Entry ET:
/START REGION MEMABC
Response ET:
DFS058I START COMMAND IN PROGRESS
Response ET:
DFS551I IFP|MESSAGE|BATCH REGION XXXXXX STARTED. ID=yy TIME=zzzz CLASSES=xxx,xxx,xxx,xxx
Explanation: The JCL stored as member XXXXXX is used to start a message processing region or batch message processing region with the classes specified by the EXEC statement parameters in MEMABC.
Entry ET:
/START RTCODE ALL
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: All the Fast Path routing codes are activated. Transactions associated with these routing codes can now be processed.
Entry ET:
/START SB
Response ET:
DFS058I START COMMAND COMPLETED
Entry ET:
/DISPLAY POOL DBAS
Response ET:
SEQUENTIAL BUFFERING: STATUS = NOT-STOPPED MAX N.A. FREE N.A. CURR 160K 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 *86253/104547*
Explanation: Sequential buffering is started.
Entry ET:
/START SUBSYS ABC
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: IMS has established a connection to the requested subsystem. It is likely that an external subsystem (not CCTL) connection message will be received at this time. If this is not the case, the /DISPLAY command can be used.
Entry ET:
/sta tmember client1 tpipe tpipesy
Response ET:
DFS058I 15:39:40 START COMMAND COMPLETED SYS3 DFS996I *IMS READY* SYS3
Entry ET:
/START TRANSACTION ALL CLASS 6
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: All transactions associated with class 6 are started.
Entry ET:
/START TRANSACTION PIT, SEED
Response ET:
DFS058I START COMMAND COMPLETED
Explanation: Transactions PIT and SEED are started.
Entry ET:
/DISPLAY USER IMSUS01 IMSUS02
Response ET:
USER ENQCT DEQCT QCT IMSUS01 0 0 0 STOPPED IMSUS02 0 0 0 STOPPED *91091/111727*
Entry ET:
R 38,/START USER IMSUS01
Response ET:
DFS058I 11:19:05 START COMMAND COMPLETED
Entry ET:
/DISPLAY USER IMSUS01 IMSUS02
Response ET:
USER ENQCT DEQCT QCT IMSUS01 0 0 0 IMSUS02 0 0 0 STOPPED *91091/113038*
Entry ET:
/START USER APPLE*
Response ET:
DFS3633 11:19:35 GENERIC PARAMETER RESOURCES NOT FOUND, NO ACTION TAKEN
Entry ET (at the active site):
/START SERVGRP
Response ET (to the active subsystem):
DFS058 START COMMAND COMPLETED
Explanation: Communications between the subsystem at the active site and the subsystem at the RSR tracking site are started.