Management of job variables
This example illustrates the use of the commands for the management of job variables:
/show-jv-attr ———————————————————————————————————————————————————————— (1) %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 %0000000 :4V05:$COGNITAS.JV.PERM.STATUS1 %0000000 :4V05:$COGNITAS.JV.PERM.STATUS2 %0000000 :4V05:$COGNITAS.JV.PERM.STATUS3 %SUM 00004 JV'S; JV-VALUE = 00000000 BYTES /create-jv jv=jv.perm.error2 ————————————————————————————————————————— (2) /show-jv-attributes jv.perm.error* ——————————————————————————————————— (3) %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 %0000000 :4V05:$COGNITAS.JV.PERM.ERROR2 %SUM 00002 JV'S; JV-VALUE = 00000000 BYTES /modify-jv jv=jv.perm.error2,set-val=c'No Error' —————————————————————— (4) /show-jv-attr jv=jv.perm.error2,inf=*all-attr ————————————————————————— (5) %0000008 :4V05:$COGNITAS.JV.PERM.ERROR2 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:14:52 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00001 JV'S; JV-VALUE = 00000008 BYTES /show-jv jv=jv.perm.error2 ———————————————————————————————————————————— (6) %No Error
(1) | All permanent job variables are output. |
(2) | The job variable JV.PERM.ERROR2 is created with default values. |
(3) | All job variables beginning with the character string “JV.PERM.ERROR” are output. |
(4) | The job variable JV.PERM.ERROR2 is given the contents 'No Error'. |
(5) | All attributes of the job variable JV.PERM.ERROR2 are output. |
(6) | The contents of the job variable JV.PERM.ERROR2 are output. |
/mod-jv-attr jv=jv.perm.error2,prot=(write-pass=c'c5aq') —————————————— (7) /modify-jv jv=jv.perm.error2,set-val=c'write error' ——————————————————— (8) % JVS04B1 PASSWORD NOT SPECIFIED. COMMAND REJECTED /add-pass password=c'c5aq' ———————————————————————————————————————————— (9) /modify-jv jv=jv.perm.error2,set-val=c'write error' /show-jv jv=jv.perm.error2 ———————————————————————————————————————————— (10) %write error /show-jv-attr jv=jv.perm.error2,inf=*all-attr ————————————————————————— (11) %0000011 :4V05:$COGNITAS.JV.PERM.ERROR2 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:17:41 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = YES SUM 00001 JV'S; JV-VALUE = 00000011 BYTES /create-jv jv=#jv.temp.t1 ————————————————————————————————————————————— (12) /show-jv-attr %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 %0000011 :4V05:$COGNITAS.JV.PERM.ERROR2 %0000000 :4V05:$COGNITAS.JV.PERM.STATUS1 %0000000 :4V05:$COGNITAS.JV.PERM.STATUS2 %0000000 :4V05:$COGNITAS.JV.PERM.STATUS3 %SUM 00005 JV'S; JV-VALUE = 00000011 BYTES /show-jv-attr jv=# —————————————————————————————————————————————————— (13) %0000000 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T1 %SUM 00001 JV'S; JV-VALUE = 00000000 BYTES /show-jv-attr select=*by-attr(password=*write-pass) ——————————————————— (14) %0000011 :4V05:$COGNITAS.JV.PERM.ERROR2 %SUM 00001 JV'S; JV-VALUE = 00000011 BYTES
(7) | The job variable JV.PERM.ERROR2 is protected against unauthorized writing by means of the password 'C5AQ' (the password is not logged). |
(8) | No new contents can be assigned to the write-protected job variable JV.PERM.ERROR2. |
(9) | To set new contents, the password had to be entered in the password table of the job. |
(10) | Output of the new contents 'write error'. |
(11) | Output of all attributes of the job variable. |
(12) | The temporary job variable JV.TEMP.1 is created. |
(13) | Output of all temporary job variables. |
(14) | Only permanent job variables which are password protected are displayed. |
/create-jv jv=jv.perm.error3,prot=(basic-acl=*std) —————————————————— (15) /show-jv-attr jv=jv.perm.error3,inf=*all-attr %0000000 :4V05:$COGNITAS.JV.PERM.ERROR3 % USER-ACC = OWNER-ONLY ACCESS = WRITE % OWNER = R W GROUP = - - OTHERS = - - % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:22:23 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00001 JV'S; JV-VALUE = 00000000 BYTES /mod-jv-attr jv=jv.perm.error3,new-name=#jv.temp.t3 ————————————————— (16) % JVS0449 ONLY DEFAULT ATTRIBUTES PERMITTED FOR TEMPORARY JOB VARIABLE. COMMAND REJECTED /mod-jv-attr jv=jv.perm.error3,new-name=#jv.temp.t3,prot=(basic-acl=*none) /show-jv-attr jv=#,inf=*all-attr %0000000 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T1 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:20:56 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %0000000 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T3 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:22:23 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00002 JV'S; JV-VALUE = 00000000 BYTES /show-jv-attr jv=#j* %0000000 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T1 %0000000 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T3 %SUM 00002 JV'S; JV-VALUE = 00000000 BYTES
(15) | The permanent job variable JV.PERM.ERROR3 is created and protected by a basic ACL. |
(16) | Renaming the permanent job variable JV.PERM.ERROR3 as the temporary job variable JV.TEMP.T3 is possible only when the protection attributes are explicitly reset to the default value. |
/delete-jv jv=#jv.temp. ————————————————————————————————————————————————— (17) % JVS0465 DELETE ALL JOB VARIABLES ':4V05:$COGNITAS.S.187.0FDB.JV.TEMP.' OF USER ID? REPLY (Y=YES; N=NO; T=TERMINATE COMMAND; ?=EXPLAIN ADDITIONAL OPTIONS)?y /delete-jv jv=jv.perm.status* ——————————————————————————————————————————— (18) % JVS0465 DELETE ALL JOB VARIABLES ':4V05:$COGNITAS.JV.PERM.STATUS*' OF USER ID? REPLY (Y=YES; N=NO; T=TERMINATE COMMAND; ?=EXPLAIN ADDITIONAL OPTIONS)?y,check=single % JVS0469 DELETE JOB VARIABLE ':4V05:$COGNITAS.JV.PERM.STATUS1'? REPLY (Y=YES; N=NO; T=TERMINATE; ,CHECK=NEW MODE)?y % JVS0469 DELETE JOB VARIABLE ':4V05:$COGNITAS.JV.PERM.STATUS2'? REPLY (Y=YES; N=NO; T=TERMINATE; ,CHECK=NEW MODE)?y % JVS0469 DELETE JOB VARIABLE ':4V05:$COGNITAS.JV.PERM.STATUS3'? REPLY (Y=YES; N=NO; T=TERMINATE; ,CHECK=NEW MODE)?y /show-jv-attr jv.perm.,inf=*all-attr %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:11:13 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %0000011 :4V05:$COGNITAS.JV.PERM.ERROR2 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:17:41 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = YES %SUM 00002 JV'S; JV-VALUE = 00000011 BYTES /mod-jv-attr jv=jv.perm.error1,prot=(basic-acl=*previous) —————————————— (19) /show-jv-attr jv.perm.error1,inf=*all-attr %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 % USER-ACC = OWNER-ONLY ACCESS = WRITE % OWNER = R W GROUP = - - OTHERS = - - % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:11:13 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00001 JV'S; JV-VALUE = 00000000 BYTES
(17) | All temporary job variables with names beginning with “JV.TEMP.” are to be deleted. |
(18) | All permanent job variables beginning with JV.PERM.STATUS are to be deleted. During deletion the check mode is changed for JV.PERM.STATUS* job variables: the check query is made for each job variable to be deleted. |
(19) | The job variable JV.PERM.ERROR1 is protected by a basic ACL, the values for which are set in accordance with the standard access control. |
/create-jv jv=jv.perm.status5,prot=(basic-acl=*std) —————————————————— (20) /show-jv-attr jv=**status5,inf=*all-attr %0000000 :4V05:$COGNITAS.JV.PERM.STATUS5 % USER-ACC = OWNER-ONLY ACCESS = WRITE % OWNER = R W GROUP = - - OTHERS = - - % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:32:25 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00001 JV'S; JV-VALUE = 00000000 BYTES /create-jv jv=jv.perm.status6 ———————————————————————————————————————— (21) /mod-jv-attr jv=jv.perm.status6,prot=(retention-period=10) /show-jv-attr jv=**status6,inf=*all-attr %0000000 :4V05:$COGNITAS.JV.PERM.STATUS6 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-14 % CRE-TIME = 14:34:54 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00001 JV'S; JV-VALUE = 00000000 BYTES /show-jv-attr select=*by-attr(basic-acl=*yes) ——————————————————————— (22) %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 %0000000 :4V05:$COGNITAS.JV.PERM.STATUS5 SUM 00002 JV'S; JV-VALUE = 00000000 BYTES /set-jv-link link=status6,jv=jv.perm.status6 /set-jv-link link=stat,jv=jv.perm.status6 ———————————————————————————— (23) /show-jv-link % LINK-NAME JV-NAME % *STAT :4V05:$COGNITAS.JV.PERM.STATUS6 % *STATUS6 :4V05:$COGNITAS.JV.PERM.STATUS6 /set-jv-link link=stat,jv=jv.perm.status5 ———————————————————————————— (24) /show-jv-link % LINK-NAME JV-NAME % *STAT :4V05:$COGNITAS.JV.PERM.STATUS5 % *STATUS6 :4V05:$COGNITAS.JV.PERM.STATUS6
(20) | The job variable JV.PERM.STATUS5 is newly created and simultaneously protected by a basic ACL in which only the owner has all access rights . |
(21) | Only job variables which are protected with a BASIC-ACL are displayed. |
(22) | The job variable JV.PERM.STATUS6 is newly created and subsequently protected against modification for ten days. |
(23) | For the job variable JV.PERM.STATUS6, two entries under the link names STATUS6 and STAT are set up in the JV-LINK table for the job. |
(24) | For the job variable JV.PERM.STATUS5, one entry is set up under the link name STAT, thereby overwriting the existing link name. |
/set-jv-link link=temp1,jv=#jv.temp.t1 ————————————————————————————————— (25) /show-jv-link % LINK-NAME JV-NAME % *STAT :4V05:$COGNITAS.JV.PERM.STATUS5 % *STATUS6 :4V05:$COGNITAS.JV.PERM.STATUS6 % *TEMP1 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T1 /show-jv-attr jv=*link(link=temp1),inf=*all-attr ——————————————————————— (26) %0000000 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T1 % USER-ACC = OWNER-ONLY ACCESS = WRITE % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:38:41 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00001 JV'S; JV-VALUE = 00000000 BYTES /del-jv jv=*link(link=status6) ————————————————————————————————————————— (27) % JVS04A3 ERROR WHEN DELETING JOB VARIABLE ':4V05:$COGNITAS.JV.PERM.STATUS6' % JVS04B6 EXPIRATION DATE FOR JOB VARIABLE NOT YET REACHED. COMMAND REJECTED /del-jv jv=*link(link=status6),ignore-prot=*expir —————————————————————— (28) /del-jv jv=jv.perm.status5,dialog-control=*jv-change ——————————————————— (29) % JVS0469 DELETE JOB VARIABLE ':4V05:$COGNITAS.JV.PERM.STATUS5'? REPLY (Y=YES; N=NO; T=TERMINATE; ,CHECK=NEW MODE)?y /show-jv-attr %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 %0000011 :4V05:$COGNITAS.JV.PERM.ERROR2 %SUM 00002 JV'S; JV-VALUE = 00000011 BYTES /show-jv-link —————————————————————————————————————————————————————————— (30) % LINK-NAME JV-NAME % *STAT :4V05:$COGNITAS.JV.PERM.STATUS5 % *STATUS6 :4V05:$COGNITAS.JV.PERM.STATUS6 % *TEMP1 :4V05:$COGNITAS.S.187.0FDB.JV.TEMP.T1
(25) | For the temporary job variable JV.TEMP.T1, an entry is set up under the link name TEMP1 . Since the job variable does not yet exist, it is newly created by the system. |
(26) | The job variables can be referenced in commands via the link names. |
(27) | The job variable JV.PERM.STATUS6 is to be deleted; it is to be referenced via its link name. The job variable cannot be deleted because its expiration date has not yet been reached. |
(28) | The job variable JV.PERM.STATUS6 can be deleted if the expiration date is not taken into consideration. |
(29) | A control query is executed for the job variable to be deleted by specifying the operand |
(30) | Although the job variables JV.PERM.STATUS5 and JV.PERM.STATUS6 were deleted, all JV-LINK entries are still present. |
/mod-jv-attr jv=jv.perm.error1,prot=(basic-acl=(owner=(read=y,write=n), group=*no-access,others=*no-access)) ——————————————————————————— (31) /show-jv-attr jv.perm.error1,inf=*all-attr %0000000 :4V05:$COGNITAS.JV.PERM.ERROR1 % USER-ACC = OWNER-ONLY ACCESS = WRITE % OWNER = R - GROUP = - - OTHERS = - - % CRE-DATE = 2010-08-04 EXPIR-DATE = 2010-08-04 % CRE-TIME = 14:11:13 EXPIR-TIME = 00:00:00 % READ-PASS = NONE % WRITE-PASS = NONE %SUM 00001 JV'S; JV-VALUE = 00000000 BYTES /del-jv jv=jv.perm.error1,dialog-control=*jv-change % JVS0469 DELETE JOB VARIABLE ':4V05:$COGNITAS.JV.PERM.ERROR1'? REPLY (Y=YES; N=NO; T=TERMINATE; ,CHECK=NEW MODE)?y % JVS04A3 ERROR WHEN DELETING JOB VARIABLE ':4V05:$COGNITAS.JV.PERM.ERROR1' % JVS04BF REQUESTED ACCESS TO JV NOT PERMITTED DUE TO EXISTING JV PROTECTION. COMMAND REJECTED /del-jv jv=jv.perm.error1,ignore-protection=*access —————————————————— (32)
(31) | The job variable is protected with a BASIC-ACL against accidental overwriting. The owner has read-only access and all other users have no access. |
(32) | When deleting the job variable JV.PERM.ERROR1, the protection attributes (here the BASIC-ACL) must be taken into considerations. |