| Ewald,
I'll answer the DCL portion of this note.
I have already changed the display to show the "original object action"
from DCL. This was a qar that I have closed.
I can change the action with no problems from DCL:
$ ABS SHOW ENV CHRIS_EE2/FULL
Execution Environment
Name - CHRIS_EE2
Version - 2
UID - E2ED8A65-9621-11D0-97ED-08002B111837
Data Safety Options - FULL_DATA_VERIFICATION,
XOR_REDUNDANCY_GROUPS, CRC_VER
IFICATION
Listing Option - NO_LISTING
Span Filesystem Options - NO FILESYSTEM SPAN
Symbolic Links Option - LINKS_ONLY
Compression Options - None
Original Object Action - RECORD_BACKUP_DATE *********************
User Profile
Node - AIM0
Cluster - EPCOT
User - <REQUESTER>
Privs -
Platform ID - 0
Access Right - None
Owner - AIM0::HEISLER
Access Right - AIM0::HEISLER
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL,
EXECUTE
Notification Method - NOTIFY_OPERATOR
Notification List - tapes
.
.
.
$ abs set env chris_ee2/action=no_change
$ abs show env chris_ee2/full
Execution Environment
Name - CHRIS_EE2
Version - 3
UID - 02A85A98-B4C8-11D0-BC26-08002B111837
Data Safety Options - FULL_DATA_VERIFICATION,
XOR_REDUNDANCY_GROUPS, CRC_VER
IFICATION
Listing Option - NO_LISTING
Span Filesystem Options - NO FILESYSTEM SPAN
Symbolic Links Option - LINKS_ONLY
Compression Options - None
Original Object Action - NO_CHANGE ***********************
User Profile
Node - AIM0
Cluster - EPCOT
User - <REQUESTER>
Privs -
Platform ID - 0
Access Right - None
Owner - AIM0::HEISLER
.
.
.
Chris
|
| Chris,
This is good news. So, we can consider this fixed in an upcoming release ?
Ewald.
-------------------------------------------------------------------------------
Transcript of my attempts to check this functionality. Here is what I did:
_TYCHE::ABS>> ABS SHOW ENV VNOABS_ENV/FULL
Execution Environment
Name - VNOABS_ENV
Version - 8
UID - 9FC111D3-B580-11D0-9D2F-AA0004002BC2
Data Safety Options - CRC_VERIFICATION
Listing Option - NO_LISTING
Span Filesystem Options - SPAN FILESYSTEMS
Symbolic Links Option - LINKS_ONLY
Compression Options - None
User Profile
Node - *
Cluster - *
User - ABS
Privs - SETPRV,TMPMBX,OPER,NETMBX
Platform ID - 0
Access Right - None
Owner - TYCHE::ABS
Access Right - TYCHE::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - ISDS01::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Agent Filesystem Options - FILE_IGNORE_WRITERS
Logging Option - NOT SUPPORTED
Number of Drives - 1
Staging Option - STAGING_ALLOWED
Retry Count - 3
Retry Interval - 20
Prologue Command - Reply/Bell/User=(Ewald,abs) "Starting VNOABS_ENV"
Epilogue Command - Reply/Bell/User=(Ewald,abs) "Ending VNOABS_ENV"
_TYCHE::ABS>> ABS SET ENV VNOABS_ENV/ACTION=NO_CHANGE
_TYCHE::ABS>> ABS SHOW ENV VNOABS_ENV/FULL
Execution Environment
Name - VNOABS_ENV
Version - 8 <-- same as above, ergo
UID - 9FC111D3-B580-11D0-9D2F-AA0004002BC2 <-- no change. Verified
. using the GUI.
. I stripped off the rest, since identical
_TYCHE::ABS>> ABS SET ENV VNOABS_ENV/ACTION=DELETE
_TYCHE::ABS>> ABS SHOW ENV VNOABS_ENV/FULL
Execution Environment
Name - VNOABS_ENV
Version - 8
UID - 9FC111D3-B580-11D0-9D2F-AA0004002BC2
_TYCHE::ABS>> ABS SET ENV VNOABS_ENV/ACTION=RECORD
_TYCHE::ABS>> ABS SHOW ENV VNOABS_ENV/FULL
Execution Environment
Name - VNOABS_ENV
Version - 8
UID - 9FC111D3-B580-11D0-9D2F-AA0004002BC2
So, there is no way to modify this from DCL here. I then did the same
from the GUI. Initial state was 'RECORD'
GUI: REC --> NO_CHA
Start Set Execution Environment
Set of Execution Environment, VNOABS_ENV Succeeded.
GUI: status is unchanged
GUI: REC --> DELETE
Start Set Execution Environment
Set of Execution Environment, VNOABS_ENV Succeeded.
GUI: status is unchanged
|
| Ewald,
Yes, this will go into the next release.
The GUI is going to be replaced in the next version, so the GUI
problem mentioned will NOT be fixed in the current GUI.
Chris
|