|
With a mouseclick you get a describtion of the screen item.
General Remarks regarding Action Codes
Action Codes are abbreviated codes consisting generally of one or two letters which perform some process on the file/Job variable in whose Action field they are placed. The process requested by this Action Code is generally carried out when the mask is transmitted (DUE/ ENTER key).
A few particular Action Codes (e.g. X [Variable Action], P [Print], E [Erase/ Delete], S [Select] ) are first assembled in an internal table. These Actions are only executed when the end of the file list appears on the screen, or the user explicitly requests it by issuing a command A [execute Actions]. The command A has the advantage with long lists that one does not have to page to the end of the list in order to execute the Action Codes.
Note:
A comparison of Action Codes and Variable Actions can be found at the beginning of Chapter 5 "Variable Actions".
%act The user-specific process specified by the mnemonic act will be executed for the marked data object.
%nact The user-specific process specified by the mnemonic act will be executed in the specified Connection n for the marked data object.
% | %? An overview of all mnemonic codes defined in the primary and secondary USERACT files. Those mnemonic codes defined in the secondary (central) USERACT file will be marked with an '*'. For further information, see below: "Hierarchy of the USERACT files".
The assignment of the mnemonic codes %act to the required process is achieved in the CFS.USERACT file. The structure of the file is described below.
CFS.USERACT file for User-specific Action Codes
The CFS administrator and individual users have the opportunity, by means of the CFS.USERACT file, of assigning alphanumeric mnemonic codes (%act) to customised processes. Each %Action Code can be linked to a BS2000 DO procedure, a CFS procedure or any other CFS command.
The CFS.USERACT file is a normal SAM file which can be created from within EDT, and which contains 3 different types of record:
- Remark records can appear at any point, and begin in column 1 with an asterisk ('*').
- Header records begin in column 1 with '$'. Column 2 contains
a '%', followed by any CFS command. It could be, for example, an E command to start a DO procedure in Enter mode under control of the Job Report System. The command can be specified together with an abbreviation (see below) of the name of the data object to be processed.
The name of the data object to be processed can be inserted in the command by using the following abbreviations:
!NAME File or Job variable name
!ELEMENT Library element without version or type
!LIBRARY Library containing the element
!TYP Library element type or Fcbtype of file
!VERS Library element version
Notes:
A header record can be up to 2048 bytes long. If, however, the USERACT file is to be processed with EDT, the maximum record length is limited to 256 bytes.
If the command E do proc is specified in a header record (e.g. $%E CFS.S. LMSLIB(ASSEMB) ), then each data object marked with the relevant Action Code %act (e.g. %ASS) will be processed in its own Enter job under control of the Job Report System. %act? will display the DO parameter mask for the procedure. If a Connection with the number n already exists to $DIALOG under CFS, (e.g. OC1/LOGON ...), then entering the Action Code %nact will cause the Enter job to be executed from within the Connection (e.g. %1ASS).
If the command FT appears in a header record without any abbreviation such as !NAME, !ELEMENT for the file or element name (e.g. $%FT ,,,HOST22,TEST2, A001,,,,*BS2000,TO,NO), then the name of the data object to be transferred will be substituted by CFS at execution time. The same functionality is achieved by the PD Action Code (see CFS.PDFILE). In contrast to %act, only one or two digit mnemonic codes are allowed for mn in PDmn.
If the command DO proc (calling a CFS procedure) appears in a header record, then it must be ensured that only one file or library element is marked with the % Action Code. If more than one data objects are marked, the % Action Code will only be executed for the last item marked.
Each header record has one or more mnemonic code records (%act) associated with it.
- 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 part, act, of the Action Code %act (act: alphanumeric, left justified, first character alphabetic).
Columns 11-80 Free text (description of the command to be executed for the Action Code %act), or blanks. A full list of these descriptions will be displayed by entering either the Action Code % or %? .
Assignment algorithm: %act <--> command created by CFS
The act mnemonic will be sought in the primary USERACT file. For the order in which the primary USERACT file is searched, see the "Hierarchy of the USERACT file" section below, points 1) to 3).
If the act mnemonic is not found in the primary USERACT file, the search will then be made on the secondary USERACT file, $userid.CFS.USERACT (see below, point 4).
If act begins with a digit, this will be interpreted as a Connection number, and the rest as the mnemonic. The command assigned to this mnemonic will then be executed from the specified Connection.
If a record with the specified description is found, the previous header record ($...) will be examined for the required command. Any abbreviations in the form !NAME, !ELEMENT, !LIBRARY, !TYP, !VERS (see above) appearing in the header record will be substituted with the relevant name segments of the marked data object.
The Action Codes % or %? can be used to display a list of all mnemonics currently defined, together with a description of their commands.
Hierarchy of the USERACT files
The USERACT file to be used by CFS is determined according to the following hierarchy:
1) Does a file exist with LINK=USERACT (/FILE ...,LINK=USERACT)?
2) If no TFT entry with the name USERACT exists, then a file with the jobname specified in the LOGON command (/.jobname LOGON ...), prefixed with 'CFS.USERACT.', will be sought. The search will begin first for the file CFS.USERACT.jobname in the current userid, then in the CFS installation userid (see 4).
3) If no Job name was specified in the LOGON command, or if the file CFS. USERACT.name does not exist, then a file CFS.USERACT will be sought under the current userid.
4) If none of the above files exist, CFS will finally search for a $userid.CFS. USERACT, where $userid is the userid under which CFS itself is cataloged.
Example of a CFS.USERACT file:
$%E !LIBRARY(ASS),!ELEMENT ASS Assemble a library element using the ASS procedure in the same library $%E $RZ.SYSPROC(COB85),!NAME COB Compile a file using the DO procedure COB85 in $RZ.SYSPROC $%FT ,,,HOSTV11,TEST2,A001,,,,*BS2000,TO,NO F11 File Transfer to Host V11 $%EDOR,!NAME EDOR Process the file with the CFS command EDOR $%DO PROC1,!NAME P1
1234 <11----------------------------------------------------------------------2048>
| |
| ÀÄÄÄ Remarks. These are displayed upon entering the
| Action Codes % or %? .
| If no description has been entered for a mnemonic
| code, then the command pertaining to that mnemonic
| (contents of the header record) will be displayed.
|
|
ÀÄÄ maximum 4 character mnemonic for the Action Codes %act
A further example of a USERACT file can be found in the CFS.S.LMSLIB library.
Request Help with Action Codes
? Help Function (Display list of available Action Codes).
For a full description of the Help system, see Chapter 24.
Hide a Line in the File List
- Hide an element from the file list. The respective entry is no longer displayed. Variable Actions in the form ON& ... will not be applied to files flagged with '-'.
CFS also uses this Action Code internally to remove those objects from the list that have been deleted with the Action Code E (Erase).
The YANK command can be used to make all hidden items visible again.
Position the Window at a Line in the File List
+P | + This line of the file list will be displayed as the first line on the screen.
-P This line of the file list will be displayed as the last line on the screen.
Mark a Name for later use in the Command Field.
* The '*' character can be used in the COMMAND field as a dummy variable for the name of a data object appearing in the file list. The * should be entered in the Action column of the file list next to the respective file. Once defined, the * <--> file, Job variable, or element name relationship will remain valid until replaced by another relationship, or erased by the CL* command.
*n Entering a number n (1 <= n <= 9) after the asterisk allows multiple abbreviations for names to be defined.
Notes:
The mapping of names to Action Codes by *, *1, *2, ..., *9 remains valid during a CFS run, even if a new file list is selected.
If elements of a PLAM library are displayed in the file list, the substitution of * in commands will be in the form lib(name). In certain cases, it is desirable to have the library name dropped when the name substitution takes place. In this case the command *E instead of * should be given.
A common cause of errors is the substitution of file/element names in a BS2000 command such as /FSTAT *XYZ*. Use the CL* (CLear *) command to prevent the substitution in these cases. This command cancels the relationship between * and the object name. * can thereafter used in commands without name substitutions taking place.
Examples:
NPLMS *,TEST
All elements will be displayed in the file list containg the string TEST in their name, and which are stored in the LMS library marked with *.
/CAT *,RETPD=0
The file marked with * will have its retention period set to 0 days. The STATE=U parameter, though not specified in the CAT command, will be supplied by CFS.
E *,TIME=100
Start an Enter job under control of the Job Report System.
If the file list consists of, for example, elements of a library PROC.ENTER, and an element J/TSOSLNK is marked with *, then the above command will have the * replaced by PROC.ENTER(TSOSLNK).
ACCESS=Read/Write for File/Job Variable
AR | AW Access Read/Write for the respective file/Job variable.
AWE Set Access to Write and insert Action Code E (Erase).
Modify Availability Status for File
AVH | AVS Availability High / Standard. Modify the availability designator of the file (from OSD V3.0).
Files designated as high availability (AVH) will automatically be stored by BS2000 on a volume reserved for such storage, such as a mirrored volume. If no such volume exists, the Action Code will be returned with an error.
Amend Access Rights (Basic Access Control List) for File/Job Variable/ PLAM Library Element
The Action Codes described below for amending the Basic Access Control Lists can be used equally well for Job variables and PLAM library elements. The userid under which a PLAM library is cataloged is regarded as the User (Owner).
BACL's are available as from BS2000 V10. LMS Version 2.0 or greater is necessary for PLAM libraries.
Refer also to the SP Action Code on page 6- regarding standard protection attributes.
This Action Code will result in the User Option BACL[F] being set when making a file list selection.
The BACL attributes displayed in the file list entries may be overwritten, and hence can be modified directly. To prohibit access by a particular user domain, a '-' character should be entered at the respective position, To allow access, the access or domain abbreviation (RWX or UGO) should be entered.
Allow Write/Read/Execute privileges for a particular group of userids.
x Domains for which the specified access rights should be granted.
U User. The owner (userid under which the file is cataloged) has access to the file.
G Group. A fixed group of userids (User Group) have access to the file.
O Others. All userids, other than the owner and the User Group have access to the file.
N None. Neither User, nor Group, nor Others (i.e. nobody) has access to the file. However, the owner of the file (User) can amend this setting at any time.
Any combination of the letters U, G, O may be specified for x. For example, the Action Code AXUGO grants Execute access rights for the file to the users under User, Group and Others (i.e. everybody).
AWNx | ARNx | AXNx
Prohibit Write/Read/Execute access rights to a particular group of users.
x Domains for which the specified access should be prohibited. For a description, see above. Any combination of the letters U, G, O can be specified for x. For example, the Action Code AWNGO entered for a file will prevent the file from being amended by users from the Group and all other userid's (Others).
AA[x] Access All.
x U | G | O:
All access types (i.e. Read/Write/Exec) are permitted for the specified domains. Any combination of the letters U, G, O can be specified for x. For example, the Action Code AAUGO will allow unrestricted access to the file by all users.
x W | R | X:
All domains (i.e. User/Group/Others) are permitted the specified type of access to the file. Any combination of the letters W, R, X can be specified for x.
Entering the Action Code AA without an x parameter will grant unrestricted access to the file to all domains.
ANx Access No.
x U | G | O:
All access types (i.e. Read/Write/Exec) will be prohibited for the specified domains. The owner (User) of the file may change this setting again at any time. Any combination of the letters U, G, O may be specified for x.
x W | R | X:
The specified access type will be prohibited for all domains (i.e. User/Group/Others). Any combination of the letters W, R, X can be specified for x.
AN No Basic Access Control List. The BACL checks are not made when accessing the file. A Standard Basic Access Control List can be reactivated, for example, by entering the AS Action Code.
AS Access Rights = Standard. A standard set of BACL attributes are applied to a file that is not yet protected by any set. The standard attributes are dependent on the previous Share= and Access= values.
Notes:
If a Basic Access Control List or a password (see below) is defined or amended for a PLAM library element using an Action Code A.., then the following checks are carried out by CFS on the library at file level: Is the file cataloged as SHARE=YES? If Yes: Is a Basic Access Control List (BACL) or a Full Access Control List (FACL) already defined for the file? If No: A BACL is generated and set to OWNER/GROUP/OTHERS=READ/ WRITE/EXEC. This ensures that the file cannot be copied to a foreign userid.
For further information regarding BACL, see page 4-.
Define Password for File/PLAM Library Element Access
Note: A prerequisite for defining READ/WRITE/EXEC passwords for PLAM library elements as described below is that LMS must be Version 2.0 or higher, and BS2000 must be Version 10.0 or higher.
ARP | AWP | AXP A mask will be displayed in which the user can enter a one to four byte Read, Write or Exec password for the respective data object (file/library element). The format is [C]'...' or X'...'.
Since passwords for library elements are stored in encrypted form, once stored, they cannot later be determined, neither by the system administrator, nor by the owner of the library. If the password is no longer known, the only solution is for the owner of the library to remove it, and specify a new password.
ARPN | AWPN | AXPN The owner, i.e. a user logged on to the userid under which the library is cataloged, can remove an existing Read, Write or Execute password for a library element. The existing password does not first have to be known. If this Action Code is to be performed on a file, the necessary password(s) must first have been entered with the PASSWORD command.
BLx The Backup Level of the file is set to the specified value.
x Backup Level: A | B | C | D | E
Copy File / Library Element / Job Variable
C Copy. The name of the data object marked with the Action Code C will be highlighted in the file list, and can be overwritten by the user with the name that the target file should have. The original data object is left unchanged. The amended line in the file list will be displayed as before after the copy has been performed.
If a file with BLKCTRL=PAMKEY is to be copied to a NK pubset, CFS will call the PAMCONV utility program internally.
Successful execution of the copy operation is indicated by C---C appearing on the right of the respective list entry. In an error occured, the respective DVS or Library error code is displayed.
A PLAM library element stored in Delta format will normally be copied as a full element. An exception is if the target element already exists in Delta format.
A PLAM element not stored in Delta format will also be copied in non-Delta format. An exception is if the target element already exists in Delta format. If so, the version will be incremented by 1.
CA Copy All. All applicable versions of a PLAM library element stored in Delta format are copied with the same structure to an element with the specified name.
CS Copy,SAME. Files/Job variables/PLAM elements are copied retaining the same protection attributes. For files and Job variables, these include the following characteristics: : ACCESS=READ/WRITE, RDPASS/WRPASS/EXPASS, RETPD, Basic Access Control List (BACL). For a PLAM library element, the Read, Write and Exec passwords, and the Basic Access Control List (BACL) will be transfered to the new element. Normally, files/Job variables/PLAM library elements are copied without taking over the protection attributes. Thus, copying a shareable file will make it non-shareable.
Notes:
If a file is to be copied from a foreign userid to the current userid, then the current userid must be prefixed to the name as $user-id. .
Copied files/library elements will be added automatically to the end of the current file list .
Display the Contents of a File / Job Variable / Library Element
D Display the contents of a data object (file/Job variable/library element).
Entering the Action Code D calls the CFS Display/Editor system, and opens the respective file/library element in read mode.
Using the M (Modify) command, the user can then amend the contents of the object. Once set, the Modify mode remains in operation until switched off with the NM (No Modify) command, or until another file is displayed with an NF (Next File) command, or until the Editor is terminated with the K1 key.
If the file or element is to be amended straight away, the Action Code M (Modify) should be given instead od D.
For a full description of the CFS Display and Editor system, see Chapter 8 "CFS Display/Editor".
Notes:
Displaying very large library elements can cause space problems on the PUBLIC discs, because CFS creates a temporary file in Public space with the name #Z[.type] [.elementname].
Display Actions are carried out immediately, in the order in which they were entered. To go from displaying one file to another, the command NF (Next File), or D should be entered in the CFS command field. The LF (Last File) command will display the previous file. To return to the file list from the Display mode, the user can enter the LST command, or simply press the K1 key (in Modify Mode, press the F1 key).
Modify Deletion Date for Files
DDn The Deletion Date for the file will be set to n days hence (0 <= n <= 999), from today. The file can be deleted by the owner from this date without reference to the protection attributes.
DS Deallocate Space. The unused storage space belonging to a file (PAM pages that have been allocated, but not written to) is released:
FILE ..., SPACE=-99999.
DS [n] Deallocate Space. The unused PAM pages allocated to the file will be released up to a multiple of n pages (0 <= n <= 999).
DS will cause all pages down to the minimum allocation to be released for files which have not yet been opened, but for which a /FILE command has been issued.
DS0 will cause all pages reserved by the file to be released completely, leaving the file without any space allocation.
Erase File / Library Element / Job Variable
E The file/library element/Job variable will be erased.
EA FGG: All file generations after the marked will be erased (ERASE... ,POS=AFTER).
EA PLAM: All delta versions (e.g. entire delta tree) of the library element will be erased.
EB FGG: All file generations before the marked will be erased (ERASE...,POS=BEFORE).
EC The catalog entry of the file will be deleted.
ED The file/library element will be erased. The space occupied by the data object will be overwritten with X'00' (ERASE... ,DESTROY>.
EDA The space occupied by the file will be released. The catalog entry will be retained (ERASE... ,DATA).
EDAR As for the EDA Action code, except that the file attributes Fcbtype, Recform, Recsize, Blksize etc. will not be reset.
EN The file/Job variable/library element is erased, and the ERT option (see notes) is explicitly switched off for the erase operation.
ET The file/Job variable/library element is erased, and the ERT option is explicitly switched on.
EI When erasing, the file attributes ACCESS=READ and RETPD>0, as well as the Basic Access Control List are ignored (ERASE... ,IGNORE=(ACCESS,EXDATE) ).
Notes:
When erasing file generations using the Action Code E, the user is asked for the POS operand.
A: POS=AFTER all File generations after the current one is erased.
B: POS=BEFORE all File generations before the current one is erased.
N: POS= no File generations will be erased.
When erasing data objects, the ERT mode of CFS (normally set on) should be noted.
The ERT Mode (Erase with Retain Tempfiles) causes files/Job variables/library elements erased with the Action Code E first to be recataloged to a temporary file. At the end of the procedure, these temporary files are erased by BS2000. From the users point of view, theses files are still physically available as files, and can be retrieved by entering FSTAT # or STAJV # in the FILENAME-SELECT field.
The names of the temporary files are created by prefixing the file to be erased with a # symbol during the CAT command.
Library elements are copied to a temporary library before the erasure, and remain accessible until the end of the procedure. The name of the temporary library is created by prefixing the library from which the element is to be erased with a # symbol.
The ERT option does not take effect if
- Files are erased with the Action Code ED (Erase ...,Destroy), EC (Erase ..., Catalog) or EN (Erase with No retain of tempfiles),
- Files are erased from private discs which have used more than 5000 pages,
- Files from another userid are erased under TSOS,
- PLAM library elements are erased with the Action Code EA (Erase All delta versions).
The ERT option may be switched off by means of the NERT (No Erase Retain Temporary) command, or via the SET mask.
If the ERT mode has been deactivated, individual files may still be erased with the Temp file option by issuing the ET Action Code (Erase with Temp files) instead of E.
Erased files are automatically removed from the current file list (implicit '-' Action Code). The YANK command can be used to make them visible again.
For PLAM elements stored in the delta form, the Action Code E will erase the displayed version. No other version is erased. After the deletion, the element will appear in the file list with the next lowest version number.
To erase all versions of the element, use the EA (Erase All) Action Code.
Process File / Library Element / Job Variable in EDT
EDT[n] | EDF[n] Process file/library element/Job variable in Format mode of EDT.
Return to the CFS mask by pressing K1 or by the H [ALT] command of EDT.
The EDT and EDF Action Codes are identical: they will both call EDT in Format mode.
Note:
The optional parameter n in the EDT/EDF/UPD Action Codes represents the EDT work file number. The specified data object is read into or updated from the specifiied work file n. If n is not specified, work file 0 will be used as standard.
EDL Process the file/library element/JV in Line mode of EDT in level 0.
Return to the CFS mask by @H [ALT] or @RET.
EDT[n]N | EDF[n]N The same as for EDT, except that the data object is re-read into the specified EDT work file. If the N option is not specified, the contents of the data object are not re-read if they are already in memory as a result of an earlier EDF/EDT Action Code. If the contents of the EDT work file were explicitly erased with @D, the object will be re-read.
EDT[n]R | EDF[n]R The same as for EDT, except that a return is made back to the CFS mask immediately after reading in the data object. The R option is useful if a data object needs to be deposited in a work file for later use (e.g. if some lines are to be copied to another work file). It can also be used to copy different library elements into various EDT work files to compare them with the COMP command in EDT, or to view them in the split screen mode of EDT.
EDT[n]S The same as for EDT, except that a file command with LINK=EDTSAM is issued. The file will be treated as one with non-standard attributes when read into EDT. An ISAM file can contain the key within the data component. For further information, see the notes below.
EDT[n]E the same as for EDT, exept that the previous contents of the EDT level are not erased when reading in the marked data object. This makes it possible to read multiple files into the EDT memory area sequentially, appending each file to the current contents.
UPD[n] Rewrite the contents of the EDT work file n to the file/library element/Job variable.
This Action Code is entered by CFS automatically in the Action Code field when returning from EDT. If the data object is not to be updated, then the Action Code should be overwritten with blanks. The individual updates are acknowledged by displaying U---U at the end of the line.
When updating an element of an ISAM LMS library with AI mode set (Automatic Increment of Version), then a new version will be created with a version number one higher than before.
EPD[n] Same effect as UPD[n], except that after the update EDT is invoked again to carry on processing the data object. The Action Code EPD can thus be used to perform an interim save of the data object.
WPD[n] Same effect as UPD[n], except that the data consistency check will not be performed. In this case, the data object will always be rewritten, even if the modification date and time stamp does not match that when the object was read. This Action Code is useful if the user has written the file explicitly with a Write command, and then later wishes to perform a UPD Action Code.
Notes:
When reading a file or PLAM library element into EDT, CFS will store the date and time of the last modification. Before the UPD Action Code is performed, a check will be performed to see whether the file has been amended since it was read in. If it has been amended, the update operation will not be performed otherwise the previous amendment will be lost. The user will be notified with an appropriate error message.
When processing files with an EDT Action Code, the user should only use the UPD Action Code to rewrite the file. If the EDT Write command is used, CFS interprets this as an amendment by another user. If the Write command has already been used, the WPD Action Code should then be used instead of UPD.
If an amendment has been made by another user, the differences can be checked as follows:
- The current contents of the file (i.e. the modifications performed by the other user) can be read into a different EDT level by means of the EDTN Action Code (e.g. EDT1N).
- EDT Compare can be used compare the two versions of the file (e.g. COMP0;9 , if the user's own amendments are in EDT level 0).
- After consolidating the user's own amendments into the version of the file in EDT level 1 (in our example), the unified file can then be rewritten in a consistent state by means of the UPD1 Action Code.
The data consistency checks which are carried out prior to the UPD Action Code being performed can be switched off by resetting an option in the CFSMAIN initialisation module.
In the event of an unexpected loss of connection (generally: the occurrence of an ABEND as a STXIT result), all non-empty EDT work files are saved automatically to backup files. The backup files will be named as follows: CFS.EDTSAV [.job name].yymmdd.hhmm.x. The x represents the EDT work file number. If a name is specified in the LOGON, this will appear in the name of the EDTSAVE files.
The next time CFS is called under that same userid, and with the same job name, the user will be notified of the existence of these EDTSAVE files.
Once set, EDT parameters such as EDIT LONG, SCALE will remain valid for the entire CFS session. The same is true for the contents of each of the EDT work files, so long as no new data is read into this work file.
When reading in another file, the line and column position of the EDT window is set to the beginning of the file.
LOWER mode in EDT: If the CFS CAP mode is set (standard), a previous LOWER ON command will be reset (LOWER OFF) when a new file or library element is read in. If the CFS LOW mode is set, then the LOWER mode of EDT will not be changed. A LOWER ON command thus entered processing a previous file will remain valid for the current file. For further information, see page 18-.
If files/library elements/Job variables are read into various work files with EDT[n], then the user will be placed in the work file specified by the last file flagged with the Action Code.
If multiple data objects are marked with the EDT Action Code, the first object will be read into EDT level 0, the second into level 1 and so on.
If files/library elements are processed with the EDT Action Code, then CFS will issue an @FILE command with the names of the respective files/library elements. Users can thus save the file/library element themselves with the W[RITE] or SA[VE] statement, as well as UPD Action Code offered by CFS.
Non-standard Files (e.g. RECFORM=F files or ISAM files with KEYPOS /KEYLEN other than 5/8) can also be processed with EDT. A manual assignment via the EDTSAM/EDTISAM link names is not necessary, since this will be provided by CFS. The record length of these files is restricted to 256.
Multiple non-standard files can be read into different EDT work files with the EDT[n] Action Code. These files can also be rewritten with the UPD[n] Action Code.
ISAM files with a keylen > 8 and any keypos can be edited and rewritten with the EDT/UPD Action Codes. The ISAM key will then not be used as the EDT line number, but will be displayed as data in each record (LINK=EDTSAM).
The ISAM key of non-standard files can thus also be edited. However, in this case the user is responsible for maintaining the ascending sequence of the key.
PLAM library elements stored in Delta format may also be processed with the EDT/UPD Action Codes, if LMS Version 1.4 or above is available. A new element with a version number incremented by one is created when a UPD is performed.
Pressing the K1 key in Format mode will return control to CFS. K1 will terminate EDT without regard to any unprocessed changes on the current screen.
Pressing the K1 key inadvertently returns the user to the CFS mask with the Action Code UPDn already filled in. It is still possible to return to EDT at the point at which it was interrupted by pressing the F1 key. This will work so long as a new file list has not been selected (NP command).
After a second exit from EDT - that is, if the user returned to EDT with F1 - the UPD Action Code will not be supplied by CFS. This must be supplied by the user if required.
If the TOM-TI editor is available in addition to EDT, the CFS system administrator can generate CFS such that the TOM-TI Editor is called instead of EDT with the EDT/EDF Action Code. In this case, the user has a number of additional commands available, such as SORT, COL, REF, DOC, FETCH.
The UPD Action Code does not have to be carried out immediately after exiting EDT. Any number of functions can be performed (including changing the list with an NP command) before UPD is executed, so long as the relevant EDT work file has not been overwritten. It can also be performed on another file in the list, or to the same file, but from a different EDT work file. The EDT work file can thus be used as a temporary storage area during a CFS session.
In Format mode of EDT, the user returns to CFS either by pressing the K1 key, or by entering the HALT command. It is also possible to add a parameter to the HALT command as follows: H [ALT] cmd. This cmd option will be interpreted as a CFS command.
Example: H CC1 Jump directly from EDT to Connection 1.
A quicker switch between EDT and Connections is possible as follows: entering the EDT command 'H n', the user will jump directly to the Connection number n. A direct return to the last EDT work file left with the H n command is achieved by pressing ^F1. Entered in a connection, ^F1 has the same effect as if F1 was pressed in the basic CFS task (Description of the F1 key - see above).
When leaving EDT with the H [ALT] cmd command, the file is not automatically updated. The user must enter UPDn if required.
THe EDT/EDF Action Codes and the EDT/EDF/EDL commands call two completely separate copies of EDT. The memory of the version of EDT called from the command line can be used as described above as another temporary storage area. The Action Codes EDT and EDF, however, use the same area of EDT.
In CFS, the INTR STXIT routine of EDT is not activated, i.e. the INTR command functions identically to the /R[esume] command.
This differs from calling EDT using using a BS2000 command in the command line: /EXEC $EDT.
If the EDT processing is interrupted by the Job Report mask, then, after ending the Job Report (K1 key, END, N), the original contents of the EDT screen may be displayed by pressing the K3 key (EDT refresh).
If the EDT/EDF Action Code is entered for a data object, then internally, the respective EDT level is first erased (@DELETE). The file is then read in, or the library element is transfered record for record into EDT memory. If, after exiting EDT, the EDT/EDF Action Code is entered next to the same data object again, then the existing EDT contents will be used (i.e. no @DELETE followed by renewed loading).
If CFS detects an empty file when performing the EDT/EDF Action Codes, or if the EDTN/EDFN (N=New) Action Codes are entered, then the object will be read in again regardless.
If the QR mode is set in CFS (standard), the virtual EDT memory is erased after an update. CFS therefore has no knowledge of whether the update was successful or not, and the virtual EDT memory is also erased if the update was not successful.
The NQR command can be used to prevent the automatic erasure of the EDT virtual memory following UPD.
Any library element type can be processed with the EDT/UPD Action codes, also R (object module) and C type (bound program) elements. C and R type elements are displayed by CFS in a special format.
Program library elements processed by EDT normally have a record type 01. If an object contains records of another type, such as those contained within R type elements (object modules), then these records will be displayed in EDT with the prefix "$RT=xxx:", where xxx is the record type. Record types range: 1 <= xxx <= 255.
Program library elements containing Format A records longer than 255 bytes, and/or Format B records can be processed by the EDT/EDF Action Codes. These records longer than 256 bytes are first split into partial records before being passed over to EDT. Trailer records will be prefixed with "$RT=CNT:". Format B records are also split into partial records before being passed over to EDT. The first EDT record for a B format record will be prefixed with "$KEY=xxxxxxxx:", where xxxxx is the record Id. The second and following EDT records making up the B Format record will be prefixed with "$KEY=Cxxxxxxx:", where xxxxx is the column number relative to the beginning of the record. When amending the data it must be remembered that the total length of the data content of a B format record must be a multiple of 2048 bytes.
ESR A screen will be displayed in which the input data for conversion or evaluation by the ESR utility will be displayed. The marked file will be used as the input file. The format of the ESR statements are described in the ESR User Manual.
This Action Code requires the ESR link library SYSLNK.ESR to be cataloged as shareable under the TSOS userid. If this is not the case, the actual name of the library can be entered at the beginning of the ESRLES module in CFSLIB.
Display File / Job Variable / PLAM Element System Information
F For a file, an FSTAT file,ALL command will be issued.
For a Job variable, a STAJV jobvar,ALL command will be issued.
For a PLAM element or an element in a ZIP archive, a special CFS status command will be issued.
For an Archive directory, a special CFS status command will be issued.
FP For a file, an FSTAT file,P command will be issued, which will display all passwords currently set for the file. Job variable passwords can also be displayed with this Action Code. The FP Action Code is only available to the system administrator under TSOS.
For an Archive directory, the Action Code F will display the following information:
% STATUS FOR :CAT2:$TSOS.LMS.PROC % % SAVE VERSION = S.941221.040250 % TYPE = FULL % % FILE VERSION = 119 % CFID = 500A7AFE % % VSN(S) = S04451 % DEVICE = TAPE-C4 % % EXP-DATE = 1996-02-01 % PLEASE ACKNOWLEDGE
For a PLAM library element (e.g. C/CFST), The Action Code F will result in the following information being displayed:
% STATUS FOR C/CFST % NAME = CFST % TYPE = C % VERSION = % VARIANT = 0001 % CREATION = 10.05.89 09:35 TSN 5681 % LAST UPD = 17.02.90 17:49 TSN 0525 % LAST ACCESS = 04.08.94 10:31 TSN % USER-DATE = 17.02.90 17:49 % ELEMENT IN HOLD BY USER-ID: CFSTEST % % PROTECTION: OWNER = R W X GROUP = - - X OTHERS = - - X % RDPASS = NO WRPASS = YES EXPASS = NO % % SPACE = 2 PAM-BLOCKS FOR 1 FORMAT-A RECORD % 269 PAM-BLOCKS FOR 35 FORMAT-B RECORDS % % FCBTYPE = PAM , RECFORM = V % % TYPE (TOTAL) OF FORMAT-A RECORDS % 11 (00001) % % ELEMENT CONTAINS NO SECONDARY NAMES % PLEASE ACKNOWLEDGE
Note:
The asterisk in the Protection line indicates that no Basic Access Control List is defined for the respective access type. This means that Owner, Group and Others have the respective access to the element.
Example above: The * in the X column of Owner, Group and Others means that no BACL is defined, and thus everybody may execute the element (/EXECL=lib,E=element).
Transfer File / PLAM Element with FT-BS2000
FT File Transfer. Transfer file/PLAM library element to a remote system with FT-BS2000. If the statements necessary for the transfer (host name, remote userid, etc.) have not been made known to CFS - either by an earlier FT command or Action Code - then these will be requested at the first FT Action Code via a mask. For a description of the mask, see the ONXFT Variable Action on page 5-.
FTM as for FT, except that the mask will always be presented in every case.
FTR As for the FT Action code, except that the mask will always be presented. This enables the file or library and element name of the transfer object to be changed on the destination system, in addition to the host name and userid.
FTS File Transfer Status. An NSTAT ... ,INFO=*ALL command is executed for the file marked with the FTS Action Code.
Instead of the FTS Action Code, U can be entered in a file list selected with the NSTAT option. This will display the current situation of the FT request. The command INSRT U will prevent the U Action Code from being deleted, as is usual, after the execution.
FTA File Transfer Activate partner. A MODIFY-FT-PARTNER ..., STATE=*ACTIV command will be executed for the partner host marked with the FTA Action Code. The Action Code can only be specified under TSOS, and only from file lists created with NSTAT.
FTC Cancel File Transfer. An NCAN command is carried out for the file flagged with the FTC Action Code, or for the displayed Transfer-Id. The respective transfer is then canceled.
FTQF File Transfer Queue First. The marked File Transfer request will be prcessed next.
FTQL File Transfer Queue Last. The marked File Transfer request will be processed last.
The Action Codes FTQF/FTQL can be used from openFT V6.0. In addition, the file list must have been created with an NSTAT [*ALL] statement in the FILENAME-SELECT field.
FTHP File Transfer High Priority. The flagged File Transfer request will be handled identically to other high priority jobs.
FTLP File Transfer Low Priority. The flagged File Transfer request will be handled identically to other low priority jobs.
FTNP File Transfer Normal Priority. The flagged File Transfer request will be handled identically to other normal priority jobs.
The FTHP/FTLP/FTNP Action Codes are only available as from openFT V6.0. A further prerequisite is that the file list was created by entering NSTAT [*ALL] in the FILENAME-SELECT field.
Notes:
Refer to the NSTAT option in the FILENAME-SELECT field of the selection mask on page 4- for information on selecting FT requests that have been started, but not yet completed.
Read Passwords for the files to be transfered with the FT Action Code will be requested dynamically by CFS.
As from version 3 of FT-BS2000, the termination of FT requests may be monitored by the Job Report System of CFS. For further information, see the JRFT/NJRFT commands on page 11-.
For further information on file transfer, in particular transfering files between BS2000 and SINIX, see Chapter 12 "File Transfer using FT-BS2000/RDAC".
Loan/Return PLAM Library Element
HOLD | NHOLD As from LMS Version 3.0, elements can be loaned from a library. This means that the userid of the borrower is marked in the library table of contents. Only users working under the userid of the borrower may amend or copy the current or higher version of the element.
The Action Code HOLD results in an element being loaned. The userid under which the loan takes place is important.
The Action Code NHOLD will reset the loan status for the element.
Note:
For a full description of the HOLD function, see the LMS User Manual Version 3.0: Chapter 3 (Elements), section 3.6 (Element protection/Data protection), "Overview of access rights for LMS actions" .
Display / Amend File Description in INF Catalog
I Inform. Display the existing documentation for the data object (file/Job variable/ library element).
IM [f] Information Modify. Create/Update the text of an entry.
f Only for creating a documentation entry: 1 to 3 letter mnemonic name of the format to be used for creating the entry.
The mask format and mnemonic code are stored in a central catalog called CFS.INF.FORMAT by the systems administrator.
IA [f] Information Add. Append an additional page of text to the entry.
f 1 to 3 letter format name for the entry.
Note: If no existing documentation exists for the indicated data object, IA will then be equivalent to IM.
II [f] Information Insert. Insert an additional page of text to the entry. This page will be inserted after the last page with the specified format.
f 1 to 3 letter format name for the entry.
Note: If no existing documentation exists for the indicated data object, IA will then be equivalent to IM.
If no text in the specified format exists, then the new page will be added after the last page (same effect as the IA Action Code - Information Add).
IE Information Erase. Delete any information text associated with the specified data object.
IEQ Information Erase with Query. The individual information pages are displayed as for the I (Inform) Action Code. This displayed page will be deleted by pressing the DUE1/Enter key. To prevent deleting the displayed page, press the K3 key. In both cases (DUE1/K3), the user is presented with the next page. The process can be interrupted by pressing K1. The last page to have been displayed will not be deleted.
IC Information Copy. Copy the entire information text. The name of a data object already documented will be requested. The copied documentation text can be then be modified (implicit IM).
For further information, see Chapter 13 "CFS File Information System".
Display File / Library Element / Job Variable in Modify Mode
M Modify the contents of a data object (file/Job variable/library element).
The Action Code M results in the CFS Display/Editor being called and the file/library element being opened in Modify mode. The Modify mode remains in effect until switched off with NM (No Modify), or an NF (Next File) command is executed for the next file flagged with D (Display)/M (Modify), or until the Editor is terminated by pressing the K1 key.
If the file/library element is only to be opened in Read mode, the D Action Code should be used instead.
For a full description of the Display/Editor system, see Chapter 8 "CFS Display/ Editor".
Notes:
Modifying very large library elements can cause space problems on PUBLIC devices, since CFS creates a temporary file for the element, called #Z[.type] [.elementname].
Modify Actions are processed, as are Display Actions, in the order in which they were specified. To display the next file, enter NF or D in the CFS command line. The LF (Last File) command can be used to return to the previously displayed file. To return to the CFS file list from Modify mode, enter the LST (List) command, or press the K1/F1 key.
Display/Amend Administration Privileges for a PLAM Library
LMS Version >= 2.0 and BS2000 >= 10.0 are prerequisites for the administration privileges described below.
The LA [xx] Action Code can be specified in the file list for PLAM libraries (FCBTYP = PL) or for any PLAM library element. In every case the result is the same: the administration privileges for the current library are displayed or amended. If the user is in a library, the element alongside which the user enters the Action Code is irrelevant.
LA The administration privileges, standard element protection attributes, and the standard element type protection attributes are displayed. The information is displayed in the following form:
% SHOW LIBRARY ADMINISTRATION + STANDARD ELEMENT-PROTECTION % % LIBRARY NAME : CFSLIB % % LAST ACCESS DATE : YES (Modify with: LAKL/LANKL) % % LIBRARY ADMINISTRATION : OWNER = YES GROUP = NO OTHERS = NO % PASSW = NO % % STD ELEMENT-PROTECTION : OWNER = R W * GROUP = - - * OTHERS = - - * % RDPASS = NO WRPASS = NO EXPASS = NO % % STD PROTECTION TYPE C/ : OWNER = R W X GROUP = - - X OTHERS = - - X % RDPASS = NO WRPASS = NO EXPASS = NO % ADMIN = OWNER OTHERS % WRITE-CONTROL = YES % % PLEASE ACKNOWLEDGE
Notes:
The asterisks in the protection lines indicate that no Basic Access Control List has been defined for the respective access type. This means that Owner, Group and Others all have the respective access to the element.
Standard element and element type protection attributes may be defined with the SP Action Code. For further information, see page 6-.
LA x [t/] Allow administration privileges for the whole library or to elements of a specified type. Administration privileges for a library allow the user to create, delete, copy and rename elements. The administration privileges may be allocated to the owner of the library (USER: Userid under which the library was created), the user group to which the owner belongs (GROUP), or all other users.
x Domains for which the administration of the library should be allowed.
U User. The owner (Userid under which the library is cataloged).
G Group. A specified number of users (User Group).
O Others. All other users.
Any combination of the letters U, G and O are allowed for x. For example, the Action-Code LAUG will grant administration privileges for the library to the userid under which the library was cataloged, and the user group.
t/ The domains (U/G/O) specified previously will have administration privileges for elements of type t . Only users within these domains have the right to amend, delete or rename type t elements.
By entering the Action Code repeatedly, administration privileges to multiple domains can be assigned. For example, LAUS/ LAOS/ will allow users from domains User and Others administration privileges to type S elements.
Type-specific administration privileges for elements are only available as from LMS Version 3.0.
LAN t/ The Action Code LANt/ will result in a previously defined administration right to type t elements being reset. Elements belonging to this type will then be governed by global administration rights.
The LA Action Code can be executed for any element in the library. The effect in all cases will be the same.
The default case, i.e. if no specific administration rights are defined for an element type, will result in the global administration rights governing the library will be valid at the element level.
LAN x Prohibit administration of the library by specified userids.
Without administration privileges for a library, elements may not be created, deleted, copied or renamed by the user.
x Domains for which administration should be prohibited. For a description, see above. Any combination of the letters U, G and O may be specified for x.
LAN All administration privileges for the library are reset. Any user with DVS access to the library may create, delete, copy and rename elements.
LAP A mask is displayed in which the user can enter a one to four byte administration password for the library. Administration activities (see above) are then only possible if this password has previously been specified with the BS2000 password command. Setting an administration password is independent of the administration domain definition using the LA x Action Code (see above).
The administration password format is [C]'...' or X'...'.
Since passwords for PLAM libraries are stored in encrypted form, they may not be displayed later, neither by the system administrator, nor by the owner of the library. If the password has been forgotten, the only solution is for the owner to delete the old password and to define a new one.
LANP The owner of the library, i.e. the userid under which the library is cataloged, can delete an administration password. The password to be deleted does not have to be known.
LAKL | LANKL Keep Last Access. Updating the Last Access Date when accessing library elements is set/reset.
The KL variation of the LA Action Code is only possible with LMS from Version 3.0.
The system administrator can set an option in the CFSMAIN module that will cause libraries created by CFS to utilise the Last Access Date function.
LAWC | LANWC Set/reset the Write Control characteristic for all elements of the same type as the element marked with the LAWC Action Code.
The WC variation of the LA Action Codes is only possible with LMS from Version 3.0.
If Write Control has been set for type t elements, the following access restrictions apply to elements of that type:
- If an element t/element/version has been loaned, i.e. it is in a HOLD state, it is not possible to amend or overwrite this element.
- Whatever the HOLD status, an element t/element/ version may not be renamed.
- The element t/element/version must be on loan (Hold Status) before a higher version of an element can be created from the current version.
Note:
If the administration privileges for a PLAM library are amended with a LA.. Action Code, the following additional checks are made by CFS: Is the library cataloged as SHARE=YES ? If so: Is a Basic Access Control List or a Full Access Control List defined for the library? If not, the BACL attributes OWNER/GROUP/OTHERS are set to READ/WRITE/EXEC. This ensures that the file may no longer be copied.
HSMS: Migration=Allowed/Inhibited
MA | MI The attribute MIGRATION= is amended for the specified file.
MA MIGRATION=ALLOWED: The file may be migrated by HSMS.
MI MIGRATION=INHIBITED: The file may not be migrated.
For further information on HSMS, see also page 4- (User Option HSMS) or page 4- (User Option MIGRATE).
Display Contents of Library or Archive Directory
Display all Element Versions
Display all Archive Save Versions of a File
NP This Action Code can be entered in the file list for:
- a library: the table of contents of the library will be displayed.
- a ZIP archive: the table of contents of the ZIP archive will be displayed as a new file list.
- an Archive directory displayed as a file: the latest save entry for files belonging to the current userid contained in this Archive directory will be displayed. See also the NPA Action Code below.
- an Archive directory list: all save entries of the marked file contained in this Archive directory will be displayed. CNS ("Cataloged but not Saved") entries will not be displayed. See also the NPA Action Code below.
- a PLAM library element saved in Delta format: all versions of the element will be displayed (User Option DELTA).
- a non-Delta PLAM library element, in so far as the element was selected with the VER User Option: all versions of the element will be displayed.
NP t [/] a PLAM library: the table of contents of only the designated element type will be displayed. For example, all source programs with element type S can be selected by entering NPS/. The terminating character '/' can be omitted if the element type to be selected is not F or L.
The Action Codes NP/NPL/NPF have the same effect as the NPLMS/LMR/FMS/DIR library command.
The Action Code NPt/ has the same effect as NPLMS library;FCB=t.
For PLAM elements stored in delta format, the Action Code NP has the same effect as the NPLMS library,element;U=DELTA command.
NPA For an Archive Directory displayed as a file: If the user is logged on under TSOS, the latest save entries for for all userids are displayed.
For an Archive Directory list entry: All save entries of the marked file contained in this Archive directory will be displayed. CNS ("Catalogued but not Saved") entries will be displayed.
Display all Tasks which have opened a File.
OPN All tasks (TSN's) which have opened the file will be displayed (utilising the OPEN User Option). A prerequisite of this Action Code is that the system administrator has started the CFS-Holder task under TSOS (/ENTER CFS.S. LMSLIB(CFSHT) ). If the file (SAM/PAM) has been opened in output mode, the current contents of the file can be displayed with the Action Code D (Display).
PS Print with parameter SPACE=E.
PB Print with parameter BINARY=YES.
PE | PSE Print with parameter ERASE.
Pn Print n copies of the file/library element.
n may be specified after any variant of the Print Action.
Printing Job Variables can only be achieved by the ONXLIST Variable Action, or with the hardcopy mode during a Display of the Job variable.
Print to a Remote Printer/Laser Printer, File Transfer, RDAC Device
PDn Print on Device. A system-specific relationship may be established between the station name of a remote printer and a one to two character mnemonic code n. This code may specified in the PD Action Code, and is defined in the CFS.PDFILE be the system administrator. Print commands with specific parameters (e.g. for a laser printer, FORM=, LOOP=, CHARS=, ..) and File Transfer/RDAC requests to a predefined host may be issued via these mnemonic codes. The record format of the CFS.PDFILE is documented in the system administrator manual in the "Administration Interfaces" section.
Any user can assign a user-specific PDFILE with a /FILE file,LINK=PDFILE command. This command can be given when starting CFS.
PDnS PD with parameter SPACE=E
PDnE PD with parameter ERASE
PDnB PD with parameter BINARY=YES
PD? A menu with the mnemonic codes and their respective printers and print parameters as defined by the system administrator will be displayed. The user can then select the required printer by marking it with an X, or S (Print with Space=E).
PD if this is the first time it is entered, it functions identically to PD?; i.e. a menu with the defined mnemonic codes and their printers will be displayed from which the user may select. In contrast to PD?, CFS will note the marked mnemonic code and substitute this automatically for each successive PD Action Code.
Rename File / Library Element / Job Variable
R Rename. The name of the data object marked in the file list with the R Action Code will be highlighted, and may be overwritten by the user with the required new name.
Pressing the F2 key will make all displayed objects overwritable, and hence able to be amended.
A successful rename operation will be acknowledged with R---R at the right end of the entry line. If an error occured, the respective DVS or library error code will be displyed.
Transfer File with RDAC / Print to Remote Printer
RD Transfer file to another system/PC, or print it out on a remote printer with RDAC/FTOS. PLAM library elements can also be printed with the RD Action Code. If the statements necessary for the file transfer (host name, remote userid, etc.) are not known to CFS - either from an earlier RDAC command/Variable Action, or by an earlier RD Action Code - then these will be requested via a mask when the RD Action Code is executed for the first time. The mask is described on page 5-: Variable Action ONXRDAC.
RDS Printing the file to a remote printere: Print with the parameter SPACE=E.
RDM RDAC transfer with an explicit request for the parameter mask (see above).
For further information on tranfering files with RDAC - in particular file transfer between BS2000 and MS-DOS systems - see Chapter 12 "File Transfer with FT-BS2000/RDAC".
Reorganise Library / ISAM File
REO Reorganise. The designated library or ISAM file is reorganised, in that all elements are transfered to a temporary file. The contents of this temporary file are then copied back to the original library (ISAM file), and the surplus disc space is released with /FILE ...,SPACE=-9999. Frequent deletions and additions to libraries create "holes" which can be removed by this REO Action. The library is "repacked" and uses less space afterwards.
REL Release Link. If files were selected on the basis of the RDTFT option in the FILENAME-SELECT field, the file list will consist of those files linked to the current process by some link name. Entering the REL Action Code in the LINK column will execute a /REL command to drop the link.
Amend RETPD for File / Job Variable
RP n Set Retention Period for File/Job variable.
n 0 <= n <= 999: Number of days for which the file/Job variable is protected from amendment.
Select: Library Element to File
S Select. An identically-named file will be created by copying the element marked with S. Multiple entries marked with S will be processed in a similar way to a Variable Action, i.e. they will be processed simultaneously at the end of the process. For further information, see the command A on page 7-.
The name of the file created will be identical to that of the library element. The element type and version description will be ignored when building the file name.
When selecting PLAM library elements to a file, only element records of Record Type 1 will be processed. Records conforming to other formats, such as those found in elements of type R, will not be transfered to the file. For further information on the record types stored in an element, see Action Code F.
SR Select with Rename. The name of the library element is displayed at half brightness, and can be amended by overwriting the current name with the required file name. In contrast to S, the SR Action Code is executed immediately.
Set Guard Protection for Files / Library Elements
SG Set Guards. Protect file/PLAM library element with Guards. If the name of the Guard profile (Read/Write/Exec Guard) has not been made known to CFS - either through an earlier GUARD command or Variable Action, or through an earlier SG/SGM Action Code - the names will be requested via a special mask the first time an SG Action Code is executed. For a description of this special mask, see the ONXGUARD Variable Action, page 5-.
SGM as for Action Code SG, except that the Guard mask will always appear.
SGN Set Guards None. The Guard protection will be removed for the specified data object. For files, this can also be achieved with the BS2000 command /MODIFY-FILE-ATTR file,PROTECTION(GUARD=*NONE).
For further information about Guard protection, see page 7-.
Show Index Attributes (NK-ISAM)
SI Show Index Attributes. The name and keypos/keylen of any existing secondary index of an NK-ISAM file are displayed.
The User Option INDEX (page 4-) and the DA (page 8-) command are also useful for handling NK-ISAM files with secondary indices.
Set Standard Protection Attributes for new PLAM Library Elements
LMS Version >= 2.0 and BS2000 >= 10.0 are prerequisites for setting standard protection attributes of new PLAM library elements as described below.
SPSTD Set Protection Standard. The protection attributes (BACL's) of the library element marked with the SPSTD Action Code will be used as the standard protection attributes for all new elements in that PLAM library.
These standard protection attributes do not apply to t/ type elements for which a protection attribute can be defined specificly (see below, Action Code SPt/). The standard protection attributes also do not apply to elements copied from another library with the CS (Copy Same) Action Code, nor to those copied with the Variable Action ONXADD.. ,CPR (Copy Protection).
The standard protection attributes currently valid can be displayed with the LA Action Code (Library Attributes, see page 6-).
SP t/ Set Protection for Type t. The protection attributes (BACL's) for the library element marked with the SP Action Code will be used as the standard protection attributes for all new type t elements in the library. If Write, Read, or Exec passwords are defined for the specified library, then these will not be transfered to the element.
SPN t/ The standard protection attributes for new elements of the specified type in this library are reset. The type-independent standard protection attributes remain as defined previously.
SPN The standard protection attributes for new elements in the library are reset. The type-dependent standard protection attributes remain as defined previously .
Notes:
If Write, Read or Exec passwords are defined for the library marked with the Action Code, these will be requested before processing the Action Code, and will be transfered as entered to the standard protection.
If the standard protection attributes for a PLAM library are defined or amended with an SP.. Action Code, the following additional checks are made by CFS: Is the library cataloged as SHARE=YES ? If so: is a Basic Access Control List or a Full Access Control List defined for the library? If not, the BACL attributes OWNER/GROUP/OTHERS are set to READ/WRITE/EXEC. This ensures that the file may not be copied.
SHARE=Yes/No for Files / Job Variables
SY | SN Share=Yes / Share=No for the specified file/Job variable.
SH | NS SHareable / NonShareable. Synonym for SY/SN.
SHS SHare=Special. The file can also be accessed by the Service userid.
SHR SHare=Yes and Access=Read.
U Update File List. The LASTP, TYP, AGE, PASS columns etc. are updated in the file list for the data objects marked with this Action Code.
This Action Code can be used for example in conjunction with the NO user option (Names Only), if the user is only interested in the attributes a few files. Entering Action Code U will insert the attributes for the specified files.
Mark for Executing a Variable Action
X The Variable Action defined in the form ONX ... will be executed on the marked data objects. If the Variable Action is specified in the form ON& ..., then the X Action Code is unneccessary, since it will automatically be carried out on all elements in the file list.
XE Mark for Variable Action, and delete the file/Job variable/element afterwards if the Variable Action is processed successfully.
If the Variable Action is not successfully processed, the E option is ignored.
The ERT option (Erase with Retain Tempfiles) is not operational with the XE Action Code, since the user is explicitly flagging the file for deletion.
Xt Only valid when including files/elements in a PLAM library: The file will be stored in the library as the specified type.
E may not be specified as an element type, since the XE Action Code would be interpreted by CFS as Erase, as described above.
Examples: XS (Type=S), XJ (Type=J).