Changing the guard path name affects:
The names of the guards to be restored themselves.
The names of the reference guards entered in these guards.
A new value can be specified for each part of the path (catalog ID, user ID, guard name part). However, whether renaming is possible depends on how the name entered with the GUARD-NAME operand is specified. Each path part can only be renamed if it is specified without using wildcards.
Example 1
The user ID MARY can be replaced with LUZIFER with the following entries:
GUARD-NAME=:XXXX:$MARY.*, NEW-PATH=(USER-ID=LUZIFER)
Example 2
Renaming is rejected with the following entries because the user ID is specified using wildcards:
GUARD-NAME=:XXXX:$*.*, NEW-PATH=(USER-ID=LUZIFER)
The following table contains a summary of the requirements that the entries in the GUARD-NAME and NEW-PATH operands must fulfil for renaming:
Wildcards in the GUARD-NAME | Entries in the NEW-PATH operand | Result | ||
User ID | Guard name part | USER-ID= | GUARD-NAME= | |
yes | yes | *SAME | *SAME | no renaming |
*SAME | <filename 1..8> | not allowed | ||
<name 1..8> | *SAME | not allowed | ||
<name 1..8> | <filename 1..8> | not allowed | ||
yes | no | *SAME | *SAME | no renaming |
*SAME | <filename 1..8> | guard name part is renamed | ||
<name 1..8> | *SAME | not allowed | ||
<name 1..8> | <filename 1..8> | not allowed | ||
no | yes | *SAME | *SAME | no renaming |
*SAME | <filename 1..8> | not allowed | ||
<name 1..8> | *SAME | user ID is renamed | ||
<name 1..8> | <filename 1..8> | not allowed | ||
no | no | *SAME | *SAME | no renaming |
*SAME | <filename 1..8> | guard name part is renamed | ||
<name 1..8> | *SAME | user ID is renamed | ||
<name 1..8> | <filename 1..8> | user ID and guard name part are renamed | ||