Commands and keywords supported on an RSR tracking subsystem
Only commands and keywords required to manage RSR tracking are supported on an RSR tracking subsystem.
For example, commands and keywords relating to transactions are not supported, because transactions are not allowed on a tracking subsystem. See Table 1 for the commands and keywords supported on an IMS™ DB/DC tracking subsystem. The subset of commands and keywords relating to databases are the only ones allowable on a DBCTL tracking subsystem.
Commands entered on an IMS tracking subsystem that are not
supported on a tracking subsystem result in message
DFS136I COMMAND xxxxxxxxxx INVALID FOR TRACKER
Commands
entered on a DCCTL tracking subsystem that are not supported on the tracking subsystem or on DCCTL
result in message
DFS136I COMMAND xxxxxxxxxx INVALID FOR DCCTL
Keywords entered on an IMS tracking subsystem that are not
supported on a tracking subsystem result in message
DFS110 COMMAND KEYWORD yyyyyyyyyyyy INVALID FOR TRACKER
Keywords entered on a DBCTL or DCCTL tracking subsystem that are not supported on a tracking
subsystem or with DBCTL or DCCTL result in message
DFS110 KEYWORD yyyyyyyyyyyy INVALID FOR DBCTL|DCCTL
The following table lists the commands and keywords that are allowed on an IMS DB/DC RSR tracking. The table also includes comments.
Commands | Keywords | Comments |
---|---|---|
/ACTIVATE | NODE | |
/ASSIGN | COMPONENT, ICOMPONENT, LINE, LTERM, NODE, PTERM, USER | |
/BROADCAST | ACTIVE, LINE, LTERM, NODE, PTERM, USER | Non-VTAM lines are not supported. |
/CANCEL | ||
/CHANGE | CPLOG | Specifies the number of system log records between system-generated checkpoints. |
/CHECKPOINT | ABDUMP, DUMPQ, FREEZE, SNAPQ, STATISTICS | Simple checkpoint (that is, with no keywords) is also supported. |
/CLSDST | NODE, USER | |
/COMPT | CNS, CRD, NODE, NOTRDY, PCH, PDS, PRT, RDR, READY, TDS, UDS, USER, VID, WPM1, WPM2, WPM3 | |
/DBRECOVERY | AREA, DATABASE, DATAGROUP, LOCAL, NOFEOV | Command only valid for a DATABASE level tracking system. Keywords only valid for areas and databases tracked at the DATABASE level. |
/DEQUEUE | LINE, LTERM, NODE, PTERM, PURGE, PURGE1, USER | |
/DIAGNOSE | ADDRESS, AREA, BLOCK, DB, JOBNAME, LINE, LINK, LTERM, MODULE, NODE, OPTION, PGM, REGION, SET, SHOW, SNAP, TRAN, USER | |
/DISPLAY | ACTIVE, AREA, ASSIGNMENT, DATABASE, DBD, DC, LINE, LTERM, MODE, MODIFY, MONITOR, NODE, OLDS, POOL, PTERM, SHUTDOWN STATUS, TRACE, TRACKING STATUS, USER, XTRC |
|
/END | LINE, NODE, PTERM, USER | |
/ERESTART | BUILDQ, CHECKPOINT, COLDBASE, COLDCOMM, COLDSYS, FORMAT, NOPASSWORD, NOTERMINAL, NOUSER, OVERRIDE, PASSWORD, TERMINAL, USER | |
/FORMAT | LTERM | |
/IDLE | LINE, NODE, NOSHUT | |
/LOG | ||
/MODIFY | ABORT, COMMIT, LTERM, PASSWORD, PREPARE, TERMINAL | The following parameters are supported: ACBLIB, BLDL, FMTLIB, MODBLKS, and RACF®. |
/NRESTART | BUILDQ, CHECKPOINT, FORMAT, NOBUILDQ, NOPASSWORD, NOTERMINAL, NOUSER, PASSWORD, TERMINAL, USER | |
/OPNDST | ID, LOGOND, MODE, NODE, Q, UDATA, USER, USERD | |
/PSTOP | LINE, LTERM, PTERM | Non-VTAM lines are not supported. |
/PURGE | LINE, LTERM, PTERM | Non-VTAM lines are not supported. |
QUERY | AREA, DB, IMS, MEMBER | |
/RCLSDST | ||
/RCOMPT | CNS, CRD, NODE, NOTRDY, PCH, PDS, PRT, RDR, READY, TDS, UDS, USER, VID, WPM1, WPM2, WPM3 | |
/RDISPLAY | ||
REFRESH USEREXIT | TYPE, MEMBER | |
/RMxxxxxx | LTERM | Only applies to tracking subsystem RECON data set. |
/RSTART | LINE, LOPEN, NODE, PTERM, USER | Non-VTAM lines are not supported. |
/RTAKEOVER | UNPLAN, NOREVERSE | |
/SIGN | ON, USERD | |
/SMCOPY | ON, TERMINAL | |
/START | AREA, AUTOARCH, DATABASE, DATAGROUP, DC, ISOLOG, LINE, LOCAL, LTERM, NODE, OLDS, PTERM, SERVGRP, USER, WADS | /START AREA, /START DATABASE, and /START DATAGROUP are only valid on a DATABASE level tracking subsystem. Non-VTAM lines are not supported. |
/STOP | ADS, AUTOARCH, DC, LINE, LTERM, NODE, OLDS, PTERM, SERVGRP, TRKAUTOARCH, USER, WADS | Non-VTAM lines are not supported. |
/SWITCH | CHECKPOINT, OLDS | |
/TEST MFS | LINE, NODE, PTERM, USER | |
/TRACE | LEVEL, LINE, MODULE,NODE, ON, OPTION, SET, TABLE, UNITYPE, USER, VOLUME | No LUMI, RETR, SCHD, or SUBS TABLE tracing is allowed on a tracking subsystem. |
UPDATE AREA | START(ACCESS), STOP(ACCESS) | |
UPDATE DATAGRP | START(ACCESS), STOP(ACCESS) | |
UPDATE DB | START(ACCESS), STOP(ACCESS) |