Managing the FDR service address space
This topic describes how to manage the FDR service address space (FDRMAIN).
Configure the FDR service address space (FDRMAIN)
You must run the FDR service address space as a started task. You must associate any started task on a z/OS system with a PROTECTED user ID. There are multiple ways for a PROTECTED user ID to be associated with a started task or procedure, and the commands involved vary depending on the ESM (External Security Manager) in use. Therefore, we recommend that you define the FDRMAIN started task to your ESM in a manner consistent with your shop standards and practices.
The FDRMAIN started task requires read access to any data sets specified in the following DD statements:
Manage the FDR service address space (FDRMAIN)
The FDR service address space (FDRMAIN) runs as a started task and is used by most of the BMC AMI Storage FDR products. This address space provides services and facilitates communication with other FDR service address spaces on other local and remote systems.
Start FDRMAIN
To start FDRMAIN.
- Verify that the JCL for the FDRMAIN started task procedure exists. Creating the FDRMAIN startup procedure describes the JCL for creating the FDRMAIN started task procedure. By default, the FDRMAIN started task procedure that is created during the installation configuration is called FDRMAIN. Your site might have defined a different FDRMAIN procedure name and library.
- From the operator console, enter the START command:
S procname[.id][,REUSASID=YES] The following console message confirms that FDRMAIN was started successfully:
FDR1000I FDRMAIN Vv.r has been successfully initialized (Build=yyyymmdd-hh.mm,RMID=rmid)
Create the FDRMAIN startup procedure
To create an FDRMAIN startup procedure:
- Copy the FDRSAMP member FDRMAIN to SYS1.PROCLIB or another system procedure library and rename this to an appropriate started task procedure name.
Follow the instructions at the top of the member to modify the procedure to your site requirements.
(Optional) Define the FDRMAIN started task procedure to your IPL procedure so that it starts at system initialization.
FDRMAIN started task procedure statements
The following table describes the list of procedure statements for FDRMAIN started tasks.
Statement | Description |
|---|---|
//procname PROC | This statement identifies the started task procedure. |
//FDRMAIN EXEC | This statement references a program named FDRMAIN that processes EXEC parameters and performs basic initialization tasks. The REGION parameter specifies the size of the private region that is required by the FDRMAIN. We recommend that you do not restrict the FDRMAIN region size. TIME=1440 defines unlimited processing time for FDRMAIN. We recommend that you do not limit the processing time for FDRMAIN. |
//STEPLIB DD | This statement defines the FDRLINK and BBLINK load libraries, which contains load modules for all BMC AMI Storage FDR products. Important: This statement should be deleted if FDRLINK and BBLINK are added to your system link list. |
//BMCPSWD DD | This statement defines the BMC product authorization (PASSWORD) Data Set. Important: When you add, modify, or remove licenses in the BMC product authorization data set you must restart FDRMAIN to complete the license installation. |
FDRMAIN started task parameter statements
The following table describes the parameter statement for FDRMAIN started tasks.
Statement | Description |
|---|---|
USEZIIP=Y|N | Specifies if eligible CPU processing should be offloaded, USEZIIP=Y, or not offloaded, USEZIIP=N, to zIIP(s) if active zIIP(s) are on the system or PROJECTCPU has been specified in IEAOPTxx. Default - USEZIIP=Y Alias - UZ= |
Operator commands
To refresh the license module or check the status of your licensed product, use the following z/OS MODIFY command:
Valid commands are as follows:
Command | Description |
|---|---|
REFRESH | Refreshes the license status after a new license module is loaded into the library, referenced by the BMCPSWD DD statement. The license is validated by the new license module. |
| STATUS | Displays the status of the current product license. |
Product license status information is displayed as follows.
--- ------- --- --- --- ----- ----- ----- ---- ---- ----------
FDR1133I YQB FDR 00 00 00 79 0 0 0 0000 YYYY-MM-DD
1) 3CC is 3 Chars Product Code
2) Product will display the Full Product Name
3) RC1 and RC2 are the return codes, If there is no license installed for a product the RC1 field will be ‘04’.
4) RC2, if there is a valid license installed, will indicate what type of license is installed and any anomalies with that license (grace period, expired, etc.)
5) PDays is the number of days remaining in a permanent license
6) TDays is the number of days remaining in a trial
7) GDays is the number of days remaining in a grace period
•The 3 days-remaining fields are mutually exclusive. It is acceptable for them to all be zero but only one should contain a number.
8) Displays the tier value of the product for which the password was generated. It is a value that is encoded as part of a permanent Password for a particular CPU ID. It usually it is used to limit the function or number of features that the product supports under the license for that CPU
9) Msg# contains the message ID of the security message that will be issued when a component is run. The message number can be compared to the current license status to ensure the correct message will be displayed. A message ID will show warning message and user will see warning message ID in JESMSGLG
10) The expiration date should be equal to today’s date plus the number of regaining days in the perm or trial license or the number of remaining grace days. If You are on perpetual License, the date will show as 0000-00-00