![]() |

Variable Actions are operations that require more parameters than simply the TSN.
The opposite of a Variable Action is an Action Code, where entering a one to five digit mnemonic code alongside the TSN will perform a simple operation on that task. For example: S (= STA), CAN (= CANCEL), etc. This type of operation requires no further parameters, or at most a simple, shortened value, such as Pnnn (= PRI tsn,nnn).
All Variable Actions begin: ONX... or ON&...
ONX... The Variable Action will only be performed on those tasks in the list explicitly marked with an Action Code X.
ON&... The Variable Action will be performed automatically on all tasks in the list without the user needing to insert an Action Code alongside any task.
For reasons of simplicity, Variable Actions will only be described in the form ONX... .
Variable Actions can also be specified in the command field of the task list. Like User Options, Variable Actions can be chained.
Example: ONX/STA !TSN,DISP=P;/STA !TSN,DISP=L
Variable Actions in Procedures
Bulk task operations can easily be performed by using Variable Actions in a DO or an Enter procedire. A DO procedure could, for example, be constructed as follows:
/PROC A /SYSFILE SYSDTA=(SYSCMD) /SETSW ON=(1,4) /EXEC CFS *002 FILE=NO TAS *002 USER OPTION=IDLE>3H;VAR=ON&/CAN !TSN AT END /SETSW OFF=(1,4) /ENDP
The above procedure will issue a CANCEL command for any task that has not been active for more than three hours.
ONX/cmd param The specified BS2000 Command, cmd, will be performed on the tasks marked with an X.
param The name of the BS2000 command to be executed should be entered here. Operands must be separated from the command by a blank. The strings !TSN and !USER-ID can be used as dummy variables, which CFS will replace with the TSN and userid under which the task is running.
Examples:
ONX/CAN !TSN
ON&/PRI !TSN,210
ONX/STA L,!USER-ID;/STA !TSN,DISP=L
Execute Console Command / Answer Console Message
ONXCONS param The specified text is sent to the Console connection opened by CFS. The data is specified as a string in param.
param If the string in param begins with a slash, '/', then the text will be interpreted as a console command. If param does not begin with a slash, then the text will be passed to the Console connection as an acknowlegement to an open question.
The strings !TSN, !USER-ID, !STATION and !PRONAME can be used in the parameter specification as dummy variables. CFS will replace the actual TSN, userid, station and processor name of the tasks marked with X.
Examples:
ONXCONS/MESS TSN=!TSN,PLEASE LOGOFF, PUBSET TEST BEING EXPORTED.
ONXCONS!TSN.N
ONXLRJ [file] The Job data relating to the Type 1 Jobs marked with X will be written to a file. This file can be used as the basis for creating a procedure to restart the Jobs in the event of a system crash.
Repeat Jobs started from a PLAM library will be displayed as the BS2000-internal Enter file name.
file Name of the file to which the Job data should be written.
Standard: TAS.RJOBLIST
Note:
For further information on repeat Jobs, see also the LRJ command on page .
ONXWATCH The Monitoring Indicator is set or reset for the tasks marked with X. The Monitoring Indicator is relevant for the WATCH User Option and for the SYSWATCH command. The WATCH User Option can be used to select all tasks for which the monitoring Indicator is set. The Monitoring Indicator is automatically set if the task is started with the JOB-PAR='TAS' parameter in the Enter/Logon command.
Display Task List Entries on the Console
The characteristics of the tasks marked with X, or all tasks if ON&TYPE is specified, will be displayed on the Console by means of the TYPE macro. Task information can thus be displayed to the operator.
By default, the output will be displayed on all consoles. The optional parameters enable the output to be handled by a Routing Code, or to be sent directly to a specific console.
<r The output will be handled by the Routing Code r (single character).
(mn) The output will be sent exclusively to the physical console with the mnemonic mn.
name The output will be sent exclusively to the logical console (DCAM application) with the specified access name.
Note:
The ONX/ON&TYPE Variable Action is only applicable to task lists, and not to other lists created with, for example, special commands such as FEP, APPL etc. To display these lists on the Console, use the EXPC command (see page ) .