|
Variable Actions are processes that require one or more parameters in addition to the name of the userid, the Pubsets and the Account numbers for their operation. An example is the JOIN command for which a large number of additional parameters cn be specified.
The counterpart to the Variable Action is the Action Code, which is a 1 to 5 character code requiring no parameters which is entered alongside the Join entry on which the operation is to be performed. For example: SU (= Show-User-Attributes), CU (= Copy User), LU (= Lock User/Sever ,SET), RU (= Remove User/Sever ,Remove), etc. Most of these operations do not require any parameters other than the name of the Join entry to be processed. For those that do, the parameters will be requested via a special mask.
All Variable Actions start with: ONX... or ON&...
ONX... The Variable Action will only be executed for those Join entries explicitly targeted by the user marking them with an X in the Action Code column.
ON&... The Variable Action will be executed automatically for all entries in the Join list, without having to enter an Action Code alongside the entries.
For the sake of simplicitly, the Variable Actions will be described in the ONX... form only.
Variable Actions can also be entered from the Join list command field (ONX..).
Suppress Variable Action Logging
Logging and displaying the Variable Actions on the screen as they are executing can significantly increase the execution time. This is particularly noticeable if large numbers of Join entries are to be processed.
If the Task Switch 14 is set to ON (/SETSW ON=14) before a Variable Action in the form ON&... is executed, the logging will be suppressed.
Bulk processing of Join entries with a Variable Action can also be performed easily in a DO or Enter procedure. An example of a DO procedure is shown below:
/PROC A
/SYSFILE SYSDTA=(SYSCMD)
/SETSW ON=(1,4,14)
/EXEC CFS
*002 FILE=NO
JES
*002 VAR=ON&LIST JES.LISTFILE,ALL
AT
END
/SETSW OFF=(1,4,14)
/ENDP
The above procedure will select all Join entries of all available online Pubsets and create a print-ready file called JES.LISTFILE containing all the Join entry attributes. Setting the Task Switch 14 will result in the messages for the individual pubsets being suppressed.
Execute a BS2000 Command for a Join Entry
ONX/cmd param A BS2000 command will be executed for the flagged Join entry.
cmd Name of the BS2000 command. The command can be specified using ISP or SDF syntax.
param The required command operands can be specified.
Help in providing the command operands can be invoked by entering ? , which will switch the user to the SDF Dialog screen. The required operands can then be selected, and these will be transferred to JES. When the command is executed, JES will provide the values for userid, PVS-Id and, if necessary, ACCNB.
When specifying parameters, the following dummy variables can be used for the userid, PVS-Id and Account number of the specified Join entry:
!UID Userid of the Join entry. !USER-ID can also be used instead of !UID.
!PVS Pubset descriptor for the Join entry. !P-V-S can also be used instead of !PVS.
!ACC Account number of the Join entry. !ACCNB can also be used instead of !ACC. The !ACC abbreviation can only be used if the Account-specific Join list has been selected.
Examples:
ONX/MODIFY-USER ?
ONX/MODIFY-USER !USER-ID,ACC-ATTR=MOD(ACC=!ACC,CPU-LIM=65000)
ONX/MODIFY-LOGON-PROT !USER-ID,P-V-S=!PVS,DIALOG-ACCESS=NO
ONX/LOCK-USER !UID,P-V-S=!PVS
ONX/MOD-POSIX-USER-ATT ?
Add Join Entry / User Group Attributes
ONXADD { UID=userid | GROUP=groupid } , PVS=pvs
Prerequisite for this Variable Action: Selection of a Join list with one of the following User Options ACCNB / SDF / CHIPCARD / TERMINAL / BAT-U-ACC.
Those Account entry/SDF-Profile/Chipcard- /Terminal entry/ userid for Batch User Access attributes marked with X will be added to the userids indicated by UID=/PVS=/ GROUP= .
If a Join list is selected without a User Option (User-specific Join list is displayed), then the userids marked with X will be added as Batch User Access userids.
userid Userid to which the Join entry attributes will be added.
groupid Description of the User group entry to which the Join entry attributes will be added.
pvs This parameter allows the Join or User group entry to be uniquely identified.
Note:
The ONXADD Variable Action can be used to copy particular characteristics from different userids to another Join entry or User group. For further information, see page (Variable Action ONXSAVE, Parameter UID=) and page (Variable Action ONXCOPYLP).
ONXJOIN param A JOIN command will be issued for the specified Join entries.
param The required JOIN command operands can be specified here. At execution time, the userid, PVSID=pvs and ACCNB=abr parameters will be substituted with the values obtained from the entry marked in the Join list.
Examples:
ONXJOIN DEFCAT=C
ONXJOIN PASS=C'xxx',PSWORD=MOD
ONXJOIN TESTPRIV=(3,1,NO)
ONXJOIN CLASS=1
This last Join command shows that parameters can be used for specific Account numbers. In this case, it is recommended that an Account number-specific Join list be created by means of the ACCNB User Option. Only then can it be guaranteed that all Account numbers belonging to a userid or PVS-ID will be processed. Only the first Account number of a userid will be displayed and processed when selected into a User-specific Join list.
ONXLIST file [, E] [, MAIL] [, SDF] [, PASS] [, ALL] [, MIN] [, ACC0] [, ACC1] [, V11]
The marked Join entries or, alternatively, all selected Join entries (ON&LIST...) will be written to a file in a print-ready format.
file Name of the file to which the list of Join entries will be written.
E An existing list will be extended (EXTEND).
MAIL The list will additionally contain the Mail addresses of the Join entries.
SDF The list will additionally contain the SDF profile of the Join entries.
PASS The list will additionally contain the logon passwords of the Join entries.
ALL The list will contain the User- and Account-specific Join entry information, as well as the Mail address, the SDF profile and the logon password.
MIN This option will suppress all empty lines, as well as the seperator lines between userids.
ACC0 No Accont number information will appear in the list.
ACC1 Only the information relating to the first Account number will appear for those Join entries possessing multiple Account numbers.
V11 The list will be prepared in a BS2000 V11-specific format.
Standard: If neither MAIL, SDF, PASS, ALL, MIN, ACC0, ACC1 nor V11 is specified, then the user-specific and account-specific information (all Account numbers) will appear in the list, without Mail addresses, SDF profiles or logon passwords, and will contain a separator line between different userids.
The parameters EX to V11 can be combined in any order.
Note:
The sequence of the Join entries in the list corresponds to the order in which they appear on the screen. This, in turn, can be determined by the value in the "SORT OPTION" field (see page ).
Examples:
ON&LIST L.JOIN.A,MIN
The user- and acount-specific information of all the Join entries in the list will be written to the file L.JOIN.A, without any separator line between the userids. The MIN parameter provides a clearer list layout, particularly when the Join entries have been selected from a single Pubset.
ON&LIST L.JOIN.FULL,ALL
All available information for the selected Join entries will be written to the file L.JOIN.FULL.
Create Procedure with ADD-/MODIFY-USER Commands
ONXSAVE file [, DO | ENTER] [, DEFCAT=[defc] ] [, PVS=[pvs] ] [, PUBSP=[val] ] [, UID= [userid] ] [, AU] [, GR] [, ACC] [, MAIL] [, NPASS] [, PASS] [, LP] [, NSTD] [, POSIX] [, SM] [, PRIV] [, OPR] [, TSET]
A BS2000 procedure containing ADD-/MODIFY-USER commands will be created. This can then be used to re-create the Join file if required.
file Name of the file to which the procedure should be written.
DO A DO procedure will be created (default).
ENTER An Enter file will be created.
DEFCAT= A DO procedure with PROC A,(&DEFC=),SUBDTA=& will be created.
The DEFAULT-PUBSET parameter in the MODIFY-USER command will be replaced with the &DEFC procedure variable value. The current value of &DEFC will be requested when the DO procedure is executed.
defc The &DEFC parameter in the DO procedure will be substituted with the value specified: PROC A,(&DEFC=defc),SUBDTA=&.
Example: DEFCAT=ABC
PVS= A DO procedure with PROC A,(&PVS=),SUBDTA=& will be created. The PUB-VOL-SET parameter in the MODIFY-USER command will be replaced with the &PVS procedure variable value. The current value of &PVS will be requested when the DO procedure is executed.
pvs The &PVS parameter in the DO procedure will be substituted with the value specified: PROC A,(&PVS=pvs),SUBDTA=&.
Example: PVS=A
PUBSP= A DO procedure with PROC A,(&PUBSP=),SUBDTA=& will be created.
The PUBSPACE parameter in the MODIFY-USER command will be replaced with the &PUBSP procedure variable value. The current value of &PUBSP will be requested when the DO procedure is executed.
val The &PUBSP parameter in the DO procedure will be substituted with the value specified: PROC A,(&PUBSP=val),SUBDTA=&.
UID= A DO procedure with PROC A,(&UID=),SUBDTA=& will be created. The userid parameter in the MODIFY-USER command will be replaced with the &UID procedure variable value. The current value of &UID will be requested when the DO procedure is executed. UID is particularly relevant when used in conjunction with the ACC parameter (see below). For instance, selected Account numbers from different Join entries can be saved together. The USER-ID= parameter is defined as a variable in the MODIFY-USER command. This procedure can thus be used later to enter particular Account numbers into different userids. For further information, see page .
userid The &UID parameter in the DO procedure will be substituted with the value specified: PROC A,(&UID=userid),SUBDTA=&.
AU The commands /ADD-USER ... /STEP will also be generated in the DO procedure under BS2000 V10 (as they are in BS2000 V11).
GR The membership of a Join entry to a particular User Group will be retained by the procedure (MODIFY-USER-GROUP ...,ADD-GROUP-MEMBER=userid command).
Standard: Group membership is not retained when the Save procedure is created.
ACC The DO procedure will be generated such that the BS2000 commands contain only the Account number information for restoring the Join entries.
Standard: The User- and Account-specific characteristics of the Join entries will normally be saved.
MAIL The DO procedure will be generated such that the BS2000 commands contain only the Mailing address information for restoring the Join entries.
Standard: The User- and Account-specific characteristics of the Join entries will normally be saved.
NPASS The DO procedure will be generated such that the existing Logon passwords will not be restored
PASS The DO procedure will be generated such that the BS2000 commands contain only the Logon password information for restoring the Join entries.
Standard: The User- and Account-specific characteristics of the Join entries will normally be saved.
LP The Logon Protection of the userid will be retained in the DO procedure (MODIFY-LOGON-PROTECTION command).
Standard: Logon Protection is not retained when the Save procedure is created.
POSIX The POSIX User attributes of the userid will be retained in the DO procedure (MODIFY-POSIX-USER-ATTRIBUTES command).
Standard: The POSIX User attributes will not normally be saved when the Save procedure is created.
SM The User Pubset attribute for SM pubsets of the userid will be retained in the DO procedure (MODIFY-USER-PUBSET-ATTRIBUTES command).
Standard: The User-Pubset attribute will not be retained when the Save procedure is created.
PRIV An Enter file containing commands for recreating the privilege levels of userids will be created.
The ONXSAVE ... ,PRIV Variable Action can only be applied to Join entries of a single pubset. Join entries from additional pubsets will be ignored.
Entering the PRIV parameter will always result in an Enter file being created. To recreate the privilege levels, the Enter file must be run under the SYSPRIV userid, since the commands may only be executed from this userid.
Standard: The privilege levels of the userids will not be taken into account when creating the procedure.
OPR An Enter file containing the commands necessary for recreating the Operator Roles of the userids will be created.
The ONXSAVE ... ,OPR Variable Action can only be applied to Join entries of a single pubset. Join entries from additional pubsets will be ignored.
Entering the OPR parameter will always result in an Enter file being created. To recreate the privilege levels, the Enter file must be run under the SYSPRIV userid, since the commands may only be executed from this userid.
Standard: The Operator Roles of the userids will not be taken into account when creating the procedure.
TSET Assigned Terminal Sets which are saved in the userids will be reflected in the DO procedure (CREATE-TERMINAL-SET procedure).
Standard: the Terminal Sets will not be taken into account.
NSTD The standard Join attributes will not be taken into account in the DO procedure. This operand allows, for example, only the Logon Protection attributes to be saved (...,LP,NSTD).
Notes:
To save all Join attributes, the Variable Action can be specified in the following format: ONXSAVE file,GR,LP,POSIX,SM
The procedure will also save entries for severed Join entries by first executing a MODIFY-USER command and then a LOCK-USER-ID command.
The DEFCAT, PVS, PUBSP and UID parameters can also be combined.
The PVS parameter is particularly useful if all Join entries from a particular pubset need to be created identically on another pubset.
The SAVE Variable Action will also process JOIN command parameters that are not catered for by SJMSAVE, such as the Account number Spool class (Parameter CLASS=) and the SEVER status of the Join entry (see the first note above).
Assign a User-Id to a User Group
ONXSETUGR group The marked Join entries will be assigned to the specified User Group (SECOS).
group Name of the User Group to which the selected Join entries should be assigned.
A /MODIFY-USER-GROUP group, ADD-GROUP-MEMBER=user-id, PUB-VOL-SET=pvs command with the specified parameters will be executed.
Examples:
ONXSETUGR GROUP1
ONXSETUGR *UNIVERSAL
Variable Actions for Logon Protection
Modify Logon Protection Attributes of Join Entries / User Groups
ONXADD UID=userid ,PVS=pvs
Prerequisite for this Variable Action: Selection of a Join list with one of the CHIPCARD/TERMINAL/BAT-U-ACC User Options.
The Chipcard/Terminal/Batch User Access entry marked with an X will be added to the userid specified by UID=/PVS= .
If the Join list is selected without one of the above User Options (i.e. if a User-specific Join list is displayed), then the userids marked will be added as Batch User Access entries.
userid Userid to which the Logon Protection attributes should be added.
pvs This parameter is used to identify uniquely the Join entry or User Group entry.
Copy Logon Protection Attributes to another Userid
ONXCOPYLP UID=user-id ,PVS=pvs , { [C] [, T] [, B] } [, RESET=Y|N]
All the Chipcard-IDs, terminals or Batch User Access attributes defined for userid and pvs will be copied to the specified userid.
userid Userid whose Chipcard-IDs, terminal or Batch User Access attributes will be copied to the marked entries.
pvs Public Volume Set of the userid.
C The Chipcard-IDs will be copied.
T The terminal entries will be copied.
B The Batch userids will be copied.
Any combination of C, T, B is possible.
RESET= Y existing entries will be reset
N the entries will be added to the existing entries
Create a Logon Protection Attribute List
ONXLISTLP file [, E] [, STD] [, NSTD] [, CID] [, PASS] [, TERM] [, TSET] [, BAT] [, ALL] [, MIN]
All, or the marked Logon Protection attributes (ON&LISTLP...) will be written to a file in a print-ready format.
file Name of the file to which the list of Join entries will be written.
E An existing file will be extended (EXTEND).
STD In the default list, all Logon Protection information will be presented except the Chipcards and terminals for Dialog access, as well as the userids permitted to perform Batch Access. The list will contain the information displayed on pages and .
NSTD The list contains only the information requested by the user. For further information, see the options listed below.
BAT The list will contain those userids allowed to perform a Batch logon.
CID The list will contain the Chipcard-IDs of the userids.
TERM The list will contain the terminals from which Dialog access to the userid is permitted.
TSET The list of Terminal Sets defined for dialog access will be displayed.
PASS The password information will be written to the file.
ALL The output file will contain all of the Logon Protections information associated with the userid.
MIN This option will suppress all empty lines, as well as the separator lines between userids.
Execute a Modify-Logon-Protection Command
ONXMLP param A MODIFY-LOGON-PROTECTION command will be executed for each of the marked entries.
param The required command operands should be specified here.
The user can enter ? to activate the SDF Dialog facility which will provide help in entering the operands. These operand values will then be accepted by JES.
At the time of execution, the current USER-ID=userid and PUB-VOL-SET=pvs values will be evaluated for the marked entry and passed as operands to the command.
Examples:
ONXMLP ?
ONXMLP PASSWORD=(ENCRYPTION=NO)
ONXMLP BATCH-ACCESS=YES(PASSWORD-CHECK=YES,ADD-USER-ACC=*ALL)
ONXMLP DIALOG-ACCESS=YES(ADD-TERMINALS=((T01,D100), (T02,D100),(T03,D100))
Create Procedure with SET-/MODIFY-LOGON-PROT Commands
ONXSAVE file [, DO | ENTER] [, DEFCAT=[defc] ] [, PVS=[pvs] ] [, PUBSP=[val] ] [, UID= [user-id] ] [, GR] [, ACC] [, LP] [, TSET] [, NSTD]
A BS2000 procedure containing SET-/MODIFY-LOGON-PROTECTION commands will be created. The Logon Protection attributes can thus be reconstructed at any time using this procedure.
LP The existing Logon Protection attributes of the userids will be retained by the DO procedure (MODIFY-LOGON-PROTECTION command).
Standard: The existing Logon Protection attributes are not retained when a Save procedure is created.
TSET The Terminal Sets assigned to the saved userids will be reflected in the DO procedure (CREATE-TERMINAL-SET command).
Standard: The Terminal Sets will not be taken into account.
NSTD The DO procedure will only save the Logon Protection attributes (MODIFY-LOGON-PROTECTION command). All other Join attributes will not be taken into account in the procedure.
For a full description of the ONXSAVE Variable Action, see page .
Example:
ON&SAVE CFS.LOGON.PROT,LP,NSTD
A DO procedure in which only the Logon Protection attributes of all Join entries will be created in a file called CFS.LOGON.PROT .
Variable Actions for POSIX User Administration
Execute a BS2000 Command for a Join Entry
A /MODIFY-POSIX-USER-ATTRIBUTES command will be executed for the marked entries.
param The required command operands should be specified here.
The user can enter ? to activate the SDF Dialog facility which will provide help in entering the operands, which in turn will be accepted by JES. JES will substitute the values for userid and PVS-Id at execution time.
Dummy variables can be used for the userid, PVS-Id and Account number when specifying parameters for the marked Join entries. These can be abbreviated as follws:
!UID Userid of the Join entry. !USER-ID can also be used instead of !UID.
!PVS Pubset identifier of the Join entry. !P-V-S can also be used instead of !PVS.
Examples:
ONX/MOD-POS-U-ATT ?
ONX/MOD-POS-USER-ATT !USER-ID,PUBSET=!PVS,GROUP-NUMBER=199
Create Procedure with /MOD-POSIX-USER-ATTR Commands
ONXSAVE file [, DO | ENTER] [, DEFCAT=[defc] ] [, PVS=[pvs] ] [, PUBSP=[val] ] [, UID= [user-id] ] [, AU] [, GR] [, ACC] [, MAIL] [, NPASS] [, LP] [, NSTD] [, POSIX]
A BS2000 procedure with /MODIFY-POSIX-USER-ATTRIBUTES commands will be created. This can be used to reconstruct the POSIX User attributes at any time.
NSTD The standard Join attributes will not be retained in the DO procedure. This operand ensures that only the POSIX User attributes are saved (...,POSIX,NSTD).
POSIX The existing POSIX User attributes of the userids will be retained in the DO procedure (MODIFY-POSIX-USER-ATTRIBUTES command).
Standard: The existing POSIX User attributes will not be taken into account when the Save procedure is created.
Example:
ON&SAVE CFS.POSIX.PROT,POSIX,NSTD
A DO procedure called CFS.POSIX.PROT will be created which will save only the POSIX User attributes of all Join entries.