Registry export utility

MAMEXPRT can be used to create the following two types of EXECs that can be used to define the source Definition Base to another system or a different Definition Base. 

• An import EXEC is created when the default.DEPLOY parameter specifies ‘N’.  You can easily modify the created import EXEC to change the exported definitions before importing them to remote sysplex Definition Bases.
• A deploy EXEC is created when the default.DEPLOY parameter specifies ‘Y’. The deploy EXEC creates a package definition which cannot be  directly modified; however, you can change the Definition Base name and the valid systems list(s).  One of the benefits of using the DEPLOY option is that it retains the attributes which are associated with generated objects in the deployment package.

If you are exporting Definition Bases that contain generated objects, then you have to use the MAMEXPRT DEPLOY(Y) option because it ensures that the attributes associated with a generated object are retained. The MAMEXPRT DEPLOY(N) option does not retain these attributes.

However, if you do not want MAMEXPRT to include generated objects, you can create an import EXEC which excludes any generated objects by specifying DEPLOY(N) and EXPORTGENERATED(N). The import EXEC that is created does not contain any generated objects. EXPORTGENERATED is only supported with the import EXEC.

MAMEXPRT requires TOM to be active on the same z/OS system where the EXEC is scheduled.

MAMEXPRT allows you to replicate object, set, and calendar definitions from one TOMPLEX to another without interrupting TOM automation processing. You can select a Definition Base in one TOMPLEX, export it to a preallocated sequential data set, copy it to another sysplex, and import it into another TOMPLEX.

To implement the Registry export utility

1. Copy EXEC MAMEXPRT from the BBSAMP data set to your UBBPROC data set.

   Important

   Copy the following BBSAMP members to the UBBPROC data set that is allocated to the SYSPROC concatenation of the BMC AMI Ops Automation PAS:

   • EXEC MAMEXPRT
   • EXEC MAMEXUPM
   • EXEC MAMEXWRM
   • EXEC MAMEXGSM
     

   If WRM (WLM Resource Management) objects are defined in the Definition Base that you are exporting, you must also copy MAMEXWRM from BBSAMP to the UBBPROC data set that is allocated to the SYSPROC concatenation of the BMC AMI OpsA PAS that is connected to the TOM PAS.

2. Edit the MAMEXPRT EXEC in ISPF to modify the parameters. Update the Beginning of required changes and Beginning of optional changes portions of the EXEC to meet your needs.
3. Schedule the MAMEXPRT EXEC from the BMC AMI OpsA PAS that is connected to the TOM PAS. Review the BMC AMI OpsA Journal to ensure the export process was completed successfully. You can also schedule the MAMEXPRT EXEC from TSO or in TSO batch. If you are executing from TSO or TSO batch, check the TSO session or the SYSTSPRT output to ensure the export process completed successfully.After MAMEXPRT completes execution, the selected TOM objects, sets, and calendar definitions will be exported and written to a new generated EXEC.
4. Review the generated EXEC and make modifications if necessary.Use caution when modifying the EXEC. If dependencies exist between objects, sets, or calendars, modifying or deleting some might affect others.

5. Schedule the generated EXEC from an BMC AMI OpsA PAS to import the exported definitions into another TOM, sysplex, or Definition Base.

   MAMEXPRT parameters

   Parameter	Description
   TOM	(optional) Determines which TOM will receive the TOMEXEC functions; parameter cannot be specified together with the TOMPLEX parameter It is recommended to omit this parameter.
   TOMPLEX	(optional) Searches to find an active TOM belonging to this TOMPLEX; parameter cannot be specified together with the TOM parameter It is recommended to omit this parameter.
   SYSPLEX	(optional) Determines from which sysplex to export definitions If not specified, definitions will be exported from the local sysplex. To export from all discovered sysplexes, specify Sysplex = '*'
   DEFBASE	(optional) Determine from which Definition Base to export definitions If not specified, definitions will be exported from the currently active Definition Base. To export from all discovered Definition Bases specify DEFBASE = '*' To bypass exporting of Definition Bases specify DEFBASE='*NO*'.
   CALBASE	(optional) Determine from which calendar Definition Base to export definitions If not specified, definitions will be exported from the currently active calendar Definition Base. To export from all discovered calendar Definition Bases specify CALBASE = '*' To bypass exporting of calendar bases specify CALBASE='*NO*'.
   DSN	Data set name that contains the output (import) REXX EXEC created by the utility If a data set name is not specified, the data set name defaults to userid.MAMEXPRT.EXEC.
   MBR	Member name in the data set (specified by the DSN parameter) that contains the output (import) REXX EXEC created by the utility If a member name is not specified, the member defaults to IMPORT00.
   REUSE	(optional) Specify Y or N (the default=N) If Y is specified, the member specified by the MBR parameter is overwritten, if it already exists. If N is specified, the member specified by MBR is not overwritten, if it already exists and the EXEC will terminate.
   DEBUG	(optional) Specify Y or N (the default=N) If Y is specified, various debugging and informational messages are written to the console and the output (import) REXX EXEC.
   V21CONV	(optional) Specify Y or N (the default=N) Specify V21CONV=Y only when you are exporting your Registry from a Registry that has been restored from a V1 or V21 Registry dump.
   EXPORTALLATTRS	(optional) Specify Y or N (the default=N) Specify EXPORTALLATTRS=Y to export all attributes, even if they are null. You can also specify this override as EXALL().
   DEPLOY	(optional) Specify Y or N (default=N) Specify DEPLOY=YES to create a member that allows you to manage Definition Base changes as a package. When you specify DEPLOY=YES, MAMEXPRT creates an EXEC that you can use to deploy Definition Base changes to a target sysplex. The target sysplex can be either the local sysplex or a remote sysplex.  If you are exporting a Definition Base that contains generated objects, you should specify DEPLOY=YES to create the deploy EXEC so that the attributes associated with generated objects are retained.  The import EXEC (DEPLOY=N or default) will not retain these attributes. If you deploy Definition Base changes to a remote sysplex, note that there might be differences in the system names between the remote and local sysplex. You should review the EXEC created by MAMEXPRT and search for the comment Beginning of optional system name changes.  Follow the instructions in this comment to specify the system names for the target sysplex.
   EXPORTGENERATED	EXPORTGENERATED (optional) Specify Y or N (default = Y) When creating an import EXEC against a Definition Base which contains generated objects, you can specify EXPORTGENERATED(N) to have generated objects excluded from the import EXEC. This parameter is valid only when DEPLOY(N) is specified. You can also specify this override as EXGEN().