Product passwords are stored in a shared partitioned data set (PDS), each password is stored in a member in the PDS, with a particular naming standard.
The first three characters of the password member name indicate the product. They are:
BBV – StopX37/II
ESA – Automation or Enterprise Storage Automation
RML - Allocation
RRT - Reporting
Permanent* and Temporary license key names or passwords for the above products start with the 3-character code above, followed by TBL3, and the last character is P for permanent* or T for temporary.
Examples:
-
BBVTBL3T – a temporary password
-
BBVTBL3P – a permanent* password
-
BBVTBLTX - a renamed PDS member, kept as a backup copy. This member ending in something other than P or T will be disregarded by the AMI Storage Allocation, Reporting, Automation and StopX37/I products.
When receiving a new password, or a temporary password, the folks who provide the passwords often suggest renaming the existing password member(s) before running the job to install the new password(s) in the partitioned data set.
Each product reads the temporary password first, if present.
*Permanent, in this context, means to be valid until the licensing contract expires.
If you compare this information to what you see as active in the started task joblog: there are point products that optionally run as part of Allocation and Reporting, which may result in seeing more functions active than just “Allocation” or “Reporting” in the started task joblog. Similarly, the initialization of the NOCATLG2 function is displayed in the started task joblog for both StopX37/II and Allocation. The default started task name is SVOS, but Customers can change this to suit their needs.