This section of the documentation describes the Com-plete operator commands in detail.
This document covers the following topics:
With the exception of the EOJ command, each command may be entered in full or may be abbreviated. The minimum abbreviation required is the number of characters necessary to uniquely identify the command. The characters needed to identify the command are underlined in the description of each command in the sections that follow.
Note:
The MODIFY (F) command and proper ID (z/OS), or the REPLID (z/VSE)
are assumed, and are not shown in command syntax in this section.
The Terminal Information Block Table (TIBTAB) defines the terminals to be used by Com-plete. The TIBTAB is loaded or generated by the Com-plete control program during Com-plete initialization.
For each local and remote terminal, the TIBTAB contains a Terminal Information Block (TIB). The TIB contains identifying information such as a one- to five-digit Terminal Identification number (TID) and a one- to eight-character Terminal Information Block Name (TIBNAME). Either the TID or TIBNAME may be used to specify a single terminal in most computer operator commands.
When a command argument specifies a user ID, the argument must be in the form:
USERID=userid
where userid is one to eight alphanumeric characters.
Note that the command will only be accepted if the user ID is currently logged onto Com-plete.
In Com-plete, groups of terminals or user IDs can be defined. A group may contain any combination of user IDs and/or terminals. For details, refer to the description of function TU of the UUTIL utility in the Com-plete Utilities documentation.
To specify a group in an operator command, enter the groupname with the command.
If a command specifies a group containing a user ID that is not logged on, Com-plete will still carry out the command for all other members of the group.
In general, to specify all terminals in the Com-plete system, the argument ALL is entered with the command. Note, however, that a TID may be defined in the TIBTAB as belonging to the group named ALL=NO. This indicates that this TID will not be considered part of the ALL grouping.
The ACCESS command is used to start up or shut down Com-plete access processing.
ACCESS START ACCESS START,FORCE ACCESS STOP
The status of the Com-plete/ACCESS interface is established during Com-plete initialization. The ACCESS operator command allows the operator to control ACCESS processing after initialization. The FORCE option can be used on the START command to force the allocation of the entry in the Adabas SVC ID table.
The START command loads, if necessary, the Adabas interface modules and initializes the ACCESS node. A subsequent STOP command causes any further access requests to the node to be rejected by the Adabas SVC with response 148. Only the STOP command issued during EOJ processing causes the node to be deactivated and the SVC communication to be terminated.
The ALLOW command enables the computer operator to enable one of three Com-plete facilities:
ALLOW,RJE ALLOW,LOGON ALLOW,LOAD
Note that the ALLOW command is normally used in conjunction with the DISALLO command after the desired facility has been disabled and it is determined that the facility should once again be enabled.
ALLOW,RJE ALLO,LOGON AL,LOAD
The CANCEL command is used to cause an abnormal termination of an online application program that is executing from a specific local or remote terminal (TID or TIBNAME), or executing under a specific user ID.
CANCEL,tid CANCEL,tibname CANCEL,userid
The CANCEL command causes termination of the application program in conversation with the specified terminal. An application program that has been rolled out of the thread while waiting for terminal I/O will not be cancelled, however, until the terminal operator presses . When the program is cancelled, the following message is displayed at the terminal:
| ABS0003 | PROGRAM XXXXXXXX CANCELLED BY COMPUTER OPERATOR |
If a Com-plete service routine or a PV program is in control at the time the CANCEL command is entered, the CANCEL request is delayed until the routine or program is completed. The operator is notified by the following message:
| ZOC00013 | CANCEL DELAYED; IN Com-plete OR PV-PROGRAM |
Entry of a second CANCEL command causes the termination of the routine or program, but may result in the loss of buffers and/or other resources.
CAN,33 CANCEL,TIB00005 CA,U=FRED
The CLOSE command causes the current Com-plete capture data set to be closed and the next data set to be opened in order to continue uninterrupted service to CAPTUR requests by application programs.
CLOSE
The CLOSE command is normally used to make the current capture data set available for access by batch jobs.
CL
The COMSEC command allows the operator to control Com-plete security processing after initialization.
COMSEC,parameters
The status of the Com-plete security system is established during Com-plete initialization. Please refer to Security and User Exit Facilities in the System Programming documentation for a full description of the available operator commands.
The DCTRL command enables the computer operator to display the terminals in the Com-plete network that have control status. Terminals may be assigned control status by use of the SETCTL command and may have control status removed by means of the UNCTL command.
DCTRL
A terminal with control status is considered to be a privileged terminal and is allowed to perform functions not normally permitted. The DCTRL command enables the computer operator to periodically monitor such terminal usage and take corrective action if needed.
DC
The DISALLO command enables the computer operator to disallow use of the following facilities by terminal users:
DISALLO,RJE DISALLO,LOGON
The DISALLO command is normally used to temporarily disable a utility function during system maintenance. The ALLOW command can be used to reenable a function.
The DISALLO command can also be used to disallow loading of load modules from the COMPLIB load library chain. This may be useful in two cases:
If, since Com-plete startup, new extents of secondary space have been allocated to any PDS concatenated to COMPLIB, members stored into these extents cannot be loaded by Com-plete unless the COMPLIB DCB is closed and re-opened. You can do this by specifying:
DISALLO,LOAD,REOPEN
After successful execution of this command, LOADs are allowed again without the need of issuing an ALLOW,LOAD command.
A PDS concatenated to COMPLIB may become full and require compression. You can temporarily disallow LOADs from COMPLIB and free the ENQ held for one of the data sets concatenated to COMPLIB by specifying:
DISALLO,LOAD,dsn
If an ENQ exists for the data set specified, the COMPLIB DCB will be closed, and the ENQ for the data set will be freed. You can now compress the data set and, after successful compression, issue an ALLOW,LOAD command to reestablish the ENQ, re-open the COMPLIB DCB and re-allow LOADs. Note that the data set is not deallocated from Com-plete by the DISALLO,LOAD command and, therefore, need not be relocated.
Note:
While LOADs are disallowed, only requests to load resident programs
or programs residing in the Com-plete lookaside buffer are satisfied. All
requests to load a module from COMPLIB while LOADs are disallowed will be
queued and the appropriate subtask(s) will be set into WAIT state until you
issue the ALLOW,LOAD operator command. Other operator commands causing modules
to be loaded, such as PGM, SERV, etc., may cause unpredictible results when
issued in the meantime.
DISALLO,RJE DISA,LOGON
The DTASKS command enables the computer operator to display the status of all Com-plete tasks.
DTASKS
For a description of the output, please refer to the command PLIST.
DT
Write a dump of the Com-plete partition to POWER.
DUMP
The ENQ command enables the computer operator to display outstanding ENQUEUES from the Com-plete threads.
ENQ,LIST,major,minor ENQ,TERM,tibnr ENQ,USER,userid ENQ,THRD,taskid ENQ,DEQ,qname,rname
The ENQ command can be used to:
Display all ENQUEUES by specifying: LIST,major,minor;
ENQ,LIST,SYSDSN
Display all ENQUEUES for a specific terminal by specifying: TERM,tibnr;
ENQ,TERM,5
Display all ENQUEUES for a specific user by specifying: USER,userid;
ENQ,USER,FRED
Display all ENQUEUES for a specific thread by specifying: THRD,taskid.
ENQ,THRD,THREAD1
Dequeue a specific ENQUEUE by specifying: DEQ,qname,rname;
ENQ,DEQ,SYSDSN,COM.V460.DATA
The EOJ command causes a logical shutdown of the Com-plete system.
EOJ EOJ,VER=password
If the system programmer specified an EOJ verification password using the EOJ,VER system parameter, that password must also be entered with the EOJ command.
Note that a logical shutdown of Com-plete can also be performed with the z/OS STOP (P) command.
If Com-plete does not come down after you have entered EOJ, try:
EOJ,FORCE
EOJ EOJ,VER=STOPCOMP
The FORCE command enables the computer operator to force the logoff of one or more Com-plete users. Before the FORCE command can be issued, a LOGOFF command must have been issued for the specified terminals or users.
FORCE,tid FORCE,tibname FORCE,userid FORCE,groupname FORCE,ALL
Before the FORCE command can be issued, a LOGOFF command must have been issued for the specified terminals or users.
FORCE,33 FO,TIB00033 FORCE,U=CUST23 F,ACCTNG FOR,ALL
The HMSG command causes Com-plete to reissue the "hello message" that is issued to all or selected terminals after Com-plete initialization.
HMSG,tid HMSG,tibname HMSG,userid HMSG,groupname HMSG,ALL
The HMSG command is useful to notify terminal users in the network of an end to a temporary interruption of service caused by execution of the IGNORE ALL or IGNORE GROUP commands. If GROUP is not specified, the hello message is sent to all terminals. Note that the message generated by the HMSG command will not interrupt a terminal in conversation.
The HMSG command can be used to issue the hello message to:
A single local terminal - by specifying either the Terminal ID (TID) or the TIBNAME;
H,33 H,TIB00005
A single user - by specifying the user ID;
HM,U=FRED
A group of terminals or user IDs - by specifying the groupname;
HMS,DATAENTY
All terminals - by specifying ALL (Note that any terminals assigned to the group ALL=NO in the TIBTAB will not be issued the hello message by the HMSG command).
H,ALL
The IGNORE command is used to immediately terminate terminal I/O to one or more terminals or lines in the Com-plete system.
IGNORE,tid IGNORE,tibname IGNORE,userid IGNORE,groupname IGNORE,ALL
The IGNORE command can be used to terminate I/O to:
A single local terminal - by specifying either the Terminal ID (TID) or the TIBNAME;
IGNORE,33 IG,TIB00005
A single user - by specifying the user ID;
IG,U=FRED
A group of terminals or user IDs - by specifying the groupname;
IGNORE,DATAENTY
All terminals - by specifying ALL (Note that any terminals assigned to the group ALL=NO in the TIBTAB will not be ignored by an IGNORE ALL command).
I,ALL
Processing VTAM terminals for which the IGNORE command has been issued depend on the options specified in the TIB definition (ACQUIRE/NOACQUIRE, SHARE/NOSHARE).
The LOGOFF command enables the computer operator to logoff one or more Com-plete users.
LOGOFF,tid LOGOFF,tibname LOGOFF,userid LOGOFF,groupname LOGOFF,ALL
The LOGOFF command can be used to logoff:
A single local terminal - by specifying either the Terminal ID (TID) or the TIBNAME;
LOGOFF,33 LO,TIB00033
A single user - by specifying the user ID;
LOGOFF,U=CUST23
A group of terminals and/or user IDs - by specifying the groupname;
L,ACCTNG
All terminals - by specifying ALL (Note that any terminals assigned to the group ALL=NO in the TIBTAB will not be logged off by the LOGOFF ALL command).
LOG,ALL
The MSG command is used to send a message to one or more terminals or users in the Com-plete system:
MSG,tid MSG,tibname MSG,userid MSG,groupname MSG,ALL
The message class used is 1 by default, but you can override this default with an option as follows:
MSG,destination,ENTER,messsage-text = Class 5 MSG,destination,IMMED,messsage-text = Class 2 MSG,destination,messsage-text = Class 1
MSG,ALL,ENTER,Com-plete Yo-Yo in 10 minutes MSG,ALL,IMMED,Urgent Com-plete Yo-Yo
Notes:
The PGM command is used to load, delete, and refresh modules that reside in the RESIDENTPAGE area of Com-plete.
PGM,DELETE,program-name PGM,LOAD,program-name PGM,REFRESH,program-name
Note that the amount of storage GETMAINed from Com-plete's region is the module size rounded up to the next 4K boundary. The REFRESH command implies a LOAD of the new copy followed by a DELETE of the old one.
Note:
Com-plete does not check to determine if there are any active
transactions using a program being either deleted or refreshed. If there are
active transactions, the effect upon those transactions will be
unpredictable.
PGM,DELETE,PGM1 PG,LOAD,PGM1 P,REFRESH,PGM1
This command will provide a list of the current tasks defined in the requested task group and the status of each.
PLIST
If no task group is supplied as a parameter to this command, all tasks of all task groups will be displayed. This command provides similar output to the UCTRL PL function. The following is a sample output resulting from this command.
09.33.15 STC06160 COMOPC0099-T COMMAND RECEIVED AT 9:33:15 FROM CONSOLE - 00 WAS PLIST 09.33.16 STC06160 COMOPC0067-T -> GrpName Status Use Wait LastOp Time Program Tid.. L 09.33.16 STC06160 COMOPC0067-T -> OC A-Run 09.33.16 STC06160 COMOPC0067-T -> TAM A-Wait USTACK 4 0 09.33.16 STC06160 COMOPC0067-T -> MSGPO A-Wait 09.33.16 STC06160 COMOPC0067-T -> PAGING A-Wait 09.33.16 STC06160 COMOPC0067-T -> FIO A-Wait 09.33.17 STC06160 COMOPC0067-T -> DEFAULT A-Wait 0 2 Wrtm USTACK 4 0 09.33.17 STC06160 COMOPC0067-T -> DEFAULT A-Wait 0 2 Coexit UPDS 4 4 09.33.17 STC06160 COMOPC0067-T -> DEFAULT A-Wait 0 2 09.33.17 STC06160 COMOPC0001-T PList command COMPLETED.
Where:
- GrpName
This is the name of the task group of which the task in question is a member. In the case of system tasks, this is the name of the system task.
- Status
This reflects the current status of the task. The status is a combination of two state indicators separated by a dash ('-'). The primary state indicator is the letter preceding the dash indicates whether the task is Active, Quiescing or Dormant by the letters A, Q and D respectively. Active in this sense indicates that the task is available to do work. When it is quiescing, it will remain active long enough to finish any work which has been started by the task while dormant tasks cannot be used and will have no secondary state associated with them. The secondary states which may occur are as follows:
Status Meaning Wait This indicates that the task is waiting. In this state, the task is waiting on new work or on events requested by programs running in threads associated with it. Run This indicates that the task is currently running a user program. Disp This indicates that the task is going through it's dispatching cycle either finishing off old work or looking for new work. - Use
This is the current use count for the task. The use count includes the current user of the task, any users for whom a wait was issued on the task and any users with an affinity for this task.
- Wait
This is the current wait count for the task. This reflects the number events upon which the task is waiting and includes two standard events those being that work has been queued to the task group work queues or to the task's own work queue.
- LastOp
This is the last Com-plete op which was issued under control of the task.
- Time
When the task has a secondary status of 'Run', this will reflect the time in seconds that this user has spent under control of the task.
- Program
This is the name of the program currently active under control of the task, or the last program to be active under control of the task if it has a secondary status of 'wait'. If the task has never been used, this will be blank, however, once it has been used, this will always contain a value.
- Tid..
This is the tid of the current TIB active under control of the task, or the last TIB to be active under control of the task if it has a secondary status of 'wait'. If the task has never been used, this will be blank, however, once it has been used, this will always contain a value.
- L
This is the level number on which the user currently active under control of the task, or the last user to be active under control of the task if it has a secondary status of 'wait', is running. If the task has never been used, this will be blank, however, once it has been used, this will always contain a value. Level '0' will be displayed for a non-Com-pass user, for a Com-pass user who is running a program while something is stacked on all possible levels or for specific programs which must run on level 0 such as ULOG.
This command will provide a list of the current queues defined in the system and the status of each.
QOVER
This command provides similar output to the UCTRL QO function. The following is a sample output resulting from this command.
COMOPC0099-* Command received at 14:32:03 from SAG was QOVER COMOPC0067-* -> Queue name Curr HWM Tim(AV) Tim(Mx) max at COMOPC0067-* -> Output Queue 0 0 0.000 0.000 COMOPC0067-* -> Input Queue 0 0 0.000 0.000 COMOPC0067-* -> Completion Queue 0 0 0.000 0.000 COMOPC0067-* -> Message Queue 0 0 0.000 0.000 COMOPC0067-* -> $SYSTEM threadSG 0 0 0.000 0.000 COMOPC0067-* -> $SYSTEM thread-Q 0 0 0.000 0.000 COMOPC0067-* -> UT0256 threadSG 0 0 0.000 0.000 COMOPC0067-* -> UT0256 thread-Q 0 1 0.019 0.036 20.10 14:29 COMOPC0067-* -> UT0512 threadSG 0 0 0.000 0.000 COMOPC0067-* -> UT0512 thread-Q 0 0 0.000 0.000 COMOPC0067-* -> SYSTEM task-grp 0 1 0.003 0.004 20.10 14:28 COMOPC0067-* -> SYSTEM task-Q 0 0 0.000 0.000 COMOPC0067-* -> DEFAULT task-grp 0 1 0.001 0.004 20.10 14:29 COMOPC0067-* -> DEFAULT task-Q 0 0 0.000 0.000 COMOPC0067-* -> DEFAULT task-Q 0 0 0.000 0.000 COMOPC0067-* -> DEFAULT task-Q 0 1 0.011 0.022 20.10 14:29
Where:
- Queue Name
This is the 16 character name of the queue for which details are provided. The first six queues are the standard system queues used by Com-plete. Following this, each of the task group's queues will follow. The first eight characters of these queue names will contain the task group name while the second eight characters indicates their purpose within the task group.
Each task group has one common work queue upon which the work is queued and that does not have an affinity to a particular TCB within the group, i.e. that can be executed on any TCB in the group. In addition, each task within the group will have its own work queue with the identifier 'TASK-Q' associated with it. These queues are used for work associated with a particular task.
- Current (in Queue)
This is the number of TIBs currently in the queue.
- HMW (in Queue)
This is the maximum number of TIBs ever in the queue at one time.
- Time in Queue (Average)
This is the average amount of time in milliseconds a TIB spent in the queue.
- Time in Queue (Max)
This is the longest time a TIB ever spent in this queue.
- Max reached at
Shows when the HWM for 'Time in Queue' was taken..
This command causes the system to quiesce.
QUIESCE
This command will result in the following:
The VTAM application will be quiesced which will prevent any further log-ons to this Com-plete('s APPL, however, current sessions will be allowed to continue to completion. If Com-plete runs as a cluster in a Parallel Sysplex, requests to establish new sessions with Com-plete's generic VTAM resource name will automatically be routed to one of the remaining parts of the cluster.
Access will be quiesced which means that any existing sessions will be allowed to continue but any new sessions will received a 'node not active' return code.
Users returning to their COM-PASS menu will be given a warning message to the effect that the system is quiescing and that they should finish their work and log off.
Once the quiesce command has been issued, Com-plete must be stopped and restarted before normal service to users can be resumed.
The RESTART command causes an immediate restart of terminal I/O to one or more terminals or lines in the Com-plete system.
RESTART,tid RESTART,tibname RESTART,groupname RESTART,ALL
The RESTART command can be used to restart I/O to:
A single local terminal - by specifying the Terminal ID (TID) or TIBNAME;
RESTART,33 RES,TIB00033
A group of terminals - by specifying the groupname;
RESTART,DATAENTY
All terminals - by specifying ALL (Note that any terminals assigned to the group ALL=NO in the TIBTAB will not be restarted with a RESTART ALL command).
R,ALL
The SERV command enables the computer operator to pass commands to a server.
SERV,[keyword],server-id,[server-parameters]
Servers can be started and terminated using this command, and requests can be sent to servers. These servers must be specified in the Com-plete sysparm SERVER. For more information of Com-plete Servers, see Com-plete Servers in the Com-plete System Programming documentation.
SERV TERM,server-id
This command terminates the specified server.
SERV INIT,server-id(,parameters)
This command initializes the specified server.
SERV server-id,server-dependent parameters
This command sends a request to the specified server.
Set one or more local or remote terminals to control status
SETCTL,tid SETCTL,tibname SETCTL,userid SETCTL,groupname SETCTL,ALL
The SETCTL command enables the computer operator to set one or more local or remote terminals to control status. A terminal with control status is considered a privileged terminal and is allowed to perform functions normally not permitted.
In addition, the SETCTL command enables the computer operator to assign control status dynamically to one or more terminals, when necessary. Note that control status assigned using the SETCTL command is in effect for the duration of the current Com-plete session only, and is removed when the user logs off or when the UNCTL command is used.
The SETCTL command can be used to assign control status to:
A single local terminal - by specifying the Terminal ID (TID) or the TIBNAME;
SETCTL,33 SE,TIB00033
A single user - by specifying the user ID;
SETCTL,U=USER33
A group of terminals and/or users - by specifying the groupname;
SET,ACCTNG
All terminals - by specifying ALL (Note that any terminals assigned to the group ALL=NO will not be given control status with a SETCTL ALL command).
SE,ALL
Note:
If a user is logged onto a terminal to which control status is
assigned with the SETCTL command, control status will be lost when the user
logs off from that terminal.
The STATS command causes the Com-plete statistics to be written to the data set specified by the SYSPRINT DDNAME in the Com-plete startup procedure.
STATS
The TASKS command can be used to attach additional operating system tasks in a Com-plete task group or to detach some of the tasks of a task group.
TASKS,task_group_name,number_of_tasks
The number_of_tasks parameter you specify is the number of tasks you wish to exist in the task group after execution of the command,notthe number of tasks you want to be attached additionally or detached!
number_of_tasks must be greater than zero and the resulting number off all processor tasks in Com-plete must not exceed the number specified or defaulted by the MAXTASKS sysparm.
TA,DEFAULT,10
This command will provide a list of the current threads defined in the requested thread group and the status of each.
TLIST,thread_group_name
If no thread group name is provided as a parameter to the request, all threads of all thread groups will be displayed. This command produces a similar output to the UCTRL TL function.
- Subgrp
This is the name of the thread subgroup of which the thread in question is a member.
- Status
This reflects the current status of the thread. The status is a combination of two state indicators separated by a dash ('-'). The primary state indicator is the letter preceding the dash indicates whether the thread is Active, Quiescing or Dormant by the letters A, Q and D respectively. Active in this sense indicates that the thread is available to do work. When it is quiescing, it will remain active long enough to finish any work which has been started in the thread, while a dormant thread cannot be used and will have no secondary state associated with it. The secondary states which may occur are as follows:
'Free' Status
This indicates that the thread is free to run other work. If there was a previous user of the thread, this state indicates that this user's program ended or has been rolled out.
'Occ' Status
The 'occupied' status indicates that the thread is available to do work, however, the user program currently occupying the thread must first be rolled out prior to starting any other new work in the thread.
'Disp' Status
This indicates that the thread is reserved and the dispatcher is currently in the process of either starting a new user program or rolling in a user program which was previously rolled out.
'Run' Status
This indicates that the user program in the thread is currently running.
'Susp' Status
This indicates that the user program has been temporarily suspended as a wait was issued either directly by the user program or indirectly by a function used by the program. In this state, the user program may not be rolled out. Internally it indicates that the operating system task associated with the work is active elsewhere. Once the condition for the wait is satisfied, the task will continue processing this work.
- Use
This is the current use count for the thread. The use count includes the current user of the thread plus any other non relocatible users previously rolled out from this thread.
- Wait
This is the current wait count for the thread. This reflects the number of users waiting to run in the thread at the present time.
- LastOp
This is the last Com-plete op which was issued in the thread.
- Time
When the thread has a secondary status of 'Susp' or 'Run', this will reflect the time in seconds that this user has spent in the thread.
- Program
This is the name of the program currently active in the thread, or the last program to be active in the thread if the thread has a status of 'free' or 'occ'. If the thread has never been used, this will be blank, however, once the thread has been used, this will always contain a value.
- Tid..
This is the tid of the current TIB active in the thread, or the last TIB to be active in the thread if the thread has a status of 'free' or 'occ'. If the thread has never been used, this will be blank, however, once the thread has been used, this will always contain a value.
- Active L
This is the level number on which the user currently active in the thread, or the last user to be active in the thread if the thread has a status of 'free' or 'occ', is running. If the thread has never been used, this will be blank, however, once the thread has been used, this will always contain a value. Level '0' will be displayed for a non-Com-pass user, for a Com-pass user who is running a program while something is stacked on all possible levels or for specific programs which must run on level 0 such as ULOG.
The UNCTL command enables the computer operator to remove control status from one or more local or remote terminals or users.
UNCTL,tid UNCTL,tibname UNCTL,userid UNCTL,groupname UNCTL,ALL
A terminal with control status is considered to be a privileged terminal and is allowed to perform functions not normally permitted. The UNCTL command enables the computer operator to remove control status dynamically from a designated terminal whenever necessary.
The UNCTL command can be used to remove control status from:
A single local terminal - by specifying the Terminal ID (TID) or the TIBNAME;
UNCTL,33 UNC,TIB00033
A single user - by specifying the user ID;
UNCTL,U=FRED
A group of terminals and/or users - by specifying the groupname;
UNC,ACCTNG
All terminals - by specifying ALL (Note that any terminals assigned to the group ALL=NO in the TIBTAB will not have control status removed by the UNCTL ALL command).
UNC,ALL
The USER command allows the computer operator to attach a specific user program and optionally pass data to that program.
USER
Programs that are started using the USER command receive passed data in the same format as if they were started by the ATTCH function in an online program.
A special parameter, UFILE, allows the computer operator to change the status of up to five files in a single input operation.
US,UFILE, status (file1,file2,....file5)
where:
| status | is the status to which the files are to be set. Possible options: BTCH, ONLN |
| file1... | are the DD/DLBL names to be changed. Up to five can be specified, separated by commas and enclosed in parentheses. If only one file is specified, the parentheses are optional. |
The UU command is used to display status and account information about one or more logged on users.
UU,tid UU,tibname UU,userid UU,groupname UU,ALL UU,ALL
The UU command can be used to display status and account information about :
A single local terminal - by specifying the Terminal ID (TID) or the TIBNAME;
UU,33 UU,TIB00005
A single user - by specifying the user ID;
UU,U=FRED
A group of terminals and/or users - by specifying the groupname;
UU,DATAENTY
All terminals - by specifying ALL
UU,ALL
The VTAM command can be used to documentationly perform certain functions upon Com-plete's VTAM interface.
VTAM,parameter
Usually, VTAM communication is started automatically during Com-plete startup and stopped during shutdown. This includes connection to a generic resource name when requested by sysparm VTAMGENERIC and disconnection from it.
The following parameters are available with the VTAM command:
| START | start VTAM communication |
| STOP | stop VTAM communication |
| QUIESCE | stop accepting new sessions, but continue serving existing ones. This function is also invoked implicitly by the QUIESCE operator command. |
| DISCONNECT | disconnect from the generic resource name if any. No new sessions will be accepted through the generic resource name. Existing sessions will continue being served. Log-on is still possible through the unique VTAM APPL-ID. This function can be used to prepare a planned downtime for one Com-plete of a cluster in a Parallel Sysplex. |
| CONNECT | Undo DISCONNECT. Reconnects to the generic resource group specified in sysparm VTAMGENERIC. |
| NOPERSIST | Disable session persistence, i.e., at VTAM STOP or shutdown all sessions are to be terminated . This makes sense only when Com-plete has been started with sysparm VTAM-PERSIST=YES. |
| PERSIST | Undo NOPERSIST. Issuing PERSIST does not turn on session persistence unless sysparm VTAM-PERSIST=YES is in effect. Note that if you issue NOPERSIST and then PERSIST, sessions established in the meantime are not recoverable. |
| EVACUATE | When issued without any following parameter, executes an implicit QUIESCE and transfers all active VTAM sessions to the generic resource group specified in sysparm VTAMGENERIC. This can be used to push out remaining user sessions prior to shutdown of one Com-plete in a cluster. Note that active applications can only “survive” the evacuation if they support recovery, and APPLICATION-RECOVERY=YES is in effect. |
| EVACUATE,userID | If there is a user session with the specified userID, it is transferred to the generic resource group specified in sysparm VTAMGENERIC. Used mainly for testing purposes. |
Each of the above parameters can be abbreviated by its first three characters.
V,START VT,STOP