%act User-defined Action Codes

%act The user-defined process identified by the mnemonic act will be executed.

%? A list of all the mnemonic codes defined in the primary and secondary USERACT files will be displayed. Those codes defined in the secondary (central) USERACT file will be denoted with '*'. For further information, see the section: "Hierarchy of the USERACT Files".

The assignment of the mnemonics %act to the required user processes takes place via the file CFS.USERACT. A description of the structure of this file follows.

CFS.USERACT file for user-defined Action Codes

The CFS.USERACT file offers the CFS administrator and each individual CFS user the possibility of assigning user-specific process operations to an alphanumeric mnemonic code (%act). Each %-Action Code can be assigned a BS2000 DO procedure, a CFS procedure or any other command.

The CFS.USERACT file is a simple SAM file created using EDT which contains 3 different types of records:

- Commentary records can appear anywhere, and have an asterisk ('*') in column 1.

- Header records begin in column 1 with '$%JES%'. A command can be entered from column 7. The command can be executed in various ways.

-    A BS2000 command can be entered in the format /cmd.

-    A BS2000 DO procedure can be started as an Enter job under control of the Job Report system if it is started in the form E procedure.

-    A JES command can be entered in the same format as in the JES command field, e.g. PUBSP !PVS

-    A command to be executed by CFS (e.g. starting a CFS procedure) should be prefixed with 'CFS'.

Example: CFSDO procedure

Each command can be enhanced by specifying parameters as abbreviations from the Join list (see below).

The command can occupy one or more continuation lines by entering a '-' character at the end of the line to be continued. A continuation line begins with a '$' and one or more blanks, and then the continuation text of the preceding line.

Additional information regarding the Join entry marked with the Action Code can be passed to the command to be executed by entering !PVS or !USER-ID.

!PVS PVS-id of the Join entry.

!USER-ID Userid of the Join entry

A mnemonic code record (%act) follows a header record.

- Mnemonic Code records begin in column 1 with an alphabetic character. The fields have the following format (see also the example below):

Columns 1-4 variable portion act of the Action Code %act (act: alphanumeric, left-justified, first character a letter.

Columns 11-80 free text (description of the command to be executed by the Action Code %act, or blanks). The summary list of all descriptions can be displayed by entering the Action Code %?.

Assignment algorithm: %act <--> created command:

A search will first be made for the mnemonic code act in the primary USERACT file. A description of the search sequence for the primary USERACT file can be found below in the section entitled "Hierarchy of the USERACT File", points 1) to 3).

If the mnemonic code act is not found in the primary USERACT file, the search will continue in the secondary USERACT file, $userid.CFS.USERACT (see below, point 4) ).

If act begins with a number, then this will be interpreted as a Connection number, and the rest as a mnemonic code. A BS2000 DO prodecure associated with this mnemonic code will then be executed from the specified Connection:

/DO procedure

If a record with the specified description is found, the preceding header record ($...) representing the command to be executed will be sought. The abbreviations in the command of the header record, such as !TSN, !USER-ID (see above) will be replaced by the respective objects.

The Action Code %? can be used to display a list of all defined mnemonic codes and their respective commands.

Hierarchy of the USERACT files

The USERACT file to be used by CFS will be determined according to the following hierarchy:

1) Does a file command with the following link entry exist: LINK=USERACT (/FILE ...,LINK=USERACT) ?

2) If no TFT entry with the name USERACT exists, then the Job name from the LOGON command (/.name LOGON ...) will be suffixed to 'CFS.USERACT.' to form the file name.

3) If no Job name was specified in the LOGON command, or a file named CFS.USERACT.name does not exist, a search will be made for a file named CFS.USERACT under the current userid.

4) If none of the above file names exist, then CFS will finally search for a file named $userid.CFS.USERACT. $userid is the userid under which CFS is located.