Changing the Sharedprefix, Prefix, Tapeprefix, or Procedure Library Name for MICS

Document ID : KB000055367
Last Modified Date : 14/02/2018
Show Technical Document Details

This document describes a method for changing the sharedprefix, prefix, tapeprefix or JCL procedure library (PROCLIB) name in MICS without using additional DASD (i.e., renaming in place). If you wish to make any of these changes by establishing a "mirror" or parallel complex, reference Administrative Newsletter AN-00089, "Creating A MICS Test Environment." This newsletter was delivered with the PSP9110 distribution package.

The instructions in this document are divided into seven sections:

  1. Making advanced preparations

  2. Renaming the MICS complex and/or unit level data sets

  3. Updating the MICS interactive environment

  4. Updating the complex level parameters and JCL

  5. Updating the unit level parameters and JCL

  6. Copying the unit level tape files

  7. Finalizing the process

Please read the document in its entirety before beginning your changes because it is a multipurpose checklist. The steps that you will execute in each section depend upon the changes you are making. The following table provides an overview of the steps you need to complete for each type of change:

 +-----------------------------------------------------------+
 |         |              |        |            |            |
 |         | Sharedprefix | Prefix | Tapeprefix |  Proclib   |
 |-----------------------------------------------------------|
 | Sect. A |      X       |   X    |     X      |     X      |
 |-----------------------------------------------------------|
 | Sect. B |      X       |   X    |    N/A     |    N/A     |
 |-----------------------------------------------------------|
 | Sect. C |      X       |   X    |     5      |     X      |
 |-----------------------------------------------------------|
 | Sect. D |      X       |  N/A   |    N/A     | 6,7,11-14  |
 |-----------------------------------------------------------|
 | Sect. E |    19,20     |   X    |   15,20    |15,16,20,21 |
 |         |  All Units   |        |            |All Units   |
 |-----------------------------------------------------------|
 | Sect. F |     N/A      |  N/A   |     X      |    N/A     |
 |-----------------------------------------------------------|
 | Sect. G |      X       |   X    |     X      |     X      |
 +-----------------------------------------------------------+

where X means review all steps in the section, N/A means skip the section, and the numbers mean complete only the listed steps.

SECTION A. MAKING ADVANCED PREPARATIONS

Step 1. If you are changing an active and operational complex, complete the following steps; otherwise proceed to step 2.

  1. Establish a schedule and timeframe for accomplishing your changes. We recommend that you wait until monthly processing has been completed in each unit before making any changes in order to complete your reporting and accounting cycles.

  2. Inform all MICS users that you will be making changes to MICS well in advance of the actual day and what those changes will entail. This action will alert your users to the fact that the data set names in their report code and user inquiries may require changes. It will also inform your users that the complex may be unavailable on the specified date.

  3. On the day of the change, make sure that all MICS operational jobs have completed successfully and that no one has the MICS Workstation Facility allocated.

  4. Ensure that you have a suitable backup of all sharedprefix and prefix data sets for the MICS complex.

  5. As a precaution, suspend processing in all MICS data base units.

SECTION B. RENAMING THE MICS COMPLEX AND/OR UNIT LEVEL DATA SETS

*************************************************************
*  Complete this section if you are changing the MICS       *
*  sharedprefix or prefix name.                             *
*************************************************************

Step 2. Use the TSO RENAME command, ISPF option 3.2 or 3.4 to rename the existing MICS data sets. Rename the complex data set names if you are changing the sharedprefix. Rename the unit level data sets if you are changing the prefix. NOTE: Omit the "MICS." node in the data set name if NOMICSLEVEL is specified next to the SHAREDPREFIX keyword value in sharedprefix.MICS.PARMS(JCLDEFC) or next to the PREFIX keyword in prefix.MICS.PARMS(JCLDEF).

      COMPLEX LEVEL DATA SETS
          sharedprefix.MICS.ASM
          sharedprefix.MICS.CAPACITY   (if CAP is installed)
          sharedprefix.MICS.CIMANAGE   (if CIM is installed)
          sharedprefix.MICS.CLIST
          sharedprefix.MICS.CNTL
          sharedprefix.MICS.DIC.TEXT
          sharedprefix.MICS.DOC.TEXT
          sharedprefix.MICS.DTFINDEX   (if EDM is installed)
          sharedprefix.MICS.GENLIB
          sharedprefix.MICS.HOLD.PARMS
       COMPLEX LEVEL DATA SETS (continued)
          sharedprefix.MICS.HOLD.USER.SOURCE
          sharedprefix.MICS.INCLLIB
          sharedprefix.MICS.INC.TEXT
          sharedprefix.MICS.ISPHLIB
          sharedprefix.MICS.ISPMLIB
          sharedprefix.MICS.ISPPLIB
          sharedprefix.MICS.ISPSLIB
          sharedprefix.MICS.ISPTLIB
          sharedprefix.MICS.LIBLOAD.CNTL  (if pre-PSP9110)
          sharedprefix.MICS.LOAD
          sharedprefix.MICS.LOCALMOD.CNTL
          sharedprefix.MICS.MACAUTOS
          sharedprefix.MICS.MACLIB
          sharedprefix.MICS.MWFPDS.DATA
          sharedprefix.MICS.PARMS
          sharedprefix.MICS.PROCLIB (if user PROCLIB employed)
          sharedprefix.MICS.PROTOLIB
          sharedprefix.MICS.PSP.ASM
          sharedprefix.MICS.PSP.CLIST
          sharedprefix.MICS.PSP.CNTL
          sharedprefix.MICS.PSP.DIC.TEXT
          sharedprefix.MICS.PSP.DOC.TEXT
          sharedprefix.MICS.PSP.GENLIB
          sharedprefix.MICS.PSP.INCLLIB
          sharedprefix.MICS.PSP.INC.TEXT
          sharedprefix.MICS.PSP.ISPHLIB
          sharedprefix.MICS.PSP.ISPMLIB
          sharedprefix.MICS.PSP.ISPPLIB
          sharedprefix.MICS.PSP.ISPSLIB
          sharedprefix.MICS.PSP.ISPTLIB
          sharedprefix.MICS.PSP.LOAD
          sharedprefix.MICS.PSP.MACAUTOS
          sharedprefix.MICS.PSP.MACLIB
          sharedprefix.MICS.PSP.PARMS
          sharedprefix.MICS.PSP.PC.TEXT
          sharedprefix.MICS.PSP.PROTOLIB
          sharedprefix.MICS.PSP.SASFLS
          sharedprefix.MICS.PSP.SOURCE
          sharedprefix.MICS.PSP.USOURCE
          sharedprefix.MICS.SASFLS
          sharedprefix.MICS.SCREENS
          sharedprefix.MICS.SOURCE
          sharedprefix.MICS.TABLES
          sharedprefix.MICS.TAPELOAD.CNTL  (PSP9110 or higher)
          sharedprefix.MICS.TAPELOAD.LOAD  (PSP9110 or higher)
          sharedprefix.MICS.TEST.INCLLIB
          sharedprefix.MICS.TEST.LOAD
          sharedprefix.MICS.TEST.SOURCE
          sharedprefix.MICS.USER.LOAD
          sharedprefix.MICS.USER.SOURCE
       UNIT LEVEL DATA SETS - If changing a unit PREFIX
          prefix.MICS.ccc.DATA
          prefix.MICS.CHECKPT.DATA
          prefix.MICS.CNTL
          prefix.MICS.DETAIL
          prefix.MICS.DETAILn
          prefix.MICS.DAYS
          prefix.MICS.DAYSn
          prefix.MICS.IMSSUS1         (if IMS is installed)
          prefix.MICS.IMSSUS2         (if IMS is installed)
          prefix.MICS.MODEL
          prefix.MICS.MONTHS
          prefix.MICS.MONTHSn
          prefix.MICS.PARMS
          prefix.MICS.RESTART.CNTL
          prefix.MICS.SPECIAL.SOURCE
          prefix.MICS.USER.LOAD
          prefix.MICS.USER.SOURCE
          prefix.MICS.WEEKS
          prefix.MICS.WEEKSn
          prefix.MICS.YEARS
          prefix.MICS.YEARSn

SECTION C. UPDATING THE MICS INTERACTIVE ENVIRONMENT

*************************************************************
*  Complete this section if you are changing the MICS       *
*  sharedprefix, prefix or PROCLIB name.  Complete only     *
*  step 5 if changing the tapeprefix.                       *
*************************************************************

Step 3. Use ISPF Option 3.1, Library Utility, to delete the following members from the NEW sharedprefix.MICS.ISPTLIB:

ICFDBTDB  ICFDBTDD  ICFDSI  MAF$DB  MAFDBCx
MAFIHTx   MAFOJTx   MAFRST  MAFRSTx MWF$PLB
MWF$SITE

where x is the identifier of each data base unit.

Step 4. Update the current MWF CLIST that invokes the MICS Workstation Facility (MWF). Change the high level qualifiers of the MICS libraries to the new sharedprefix name.

  1. Execute the newly modified CLIST and invoke the MICS Workstation Facility (MWF). The MICS Administrator Facility Parameter panel (see
    sample below) will be displayed because the MWF$SITE member has been deleted.

    Note: The options on the MICS Administrator Facility Parameter panel depend upon your PSP maintenance level. The options on your panel may be slightly different from the ones shown in this sample.

    ------------------- MICS Administrator Facility Parameters --------
    Option ===>
    This is the first invocation of MICS. Site Table data entry required.
    1. MICS Data Sets for ISPF Applications Specify sharedprefix, ISPF tables data set name, and DDNAMEs

    2. MICS Global Parameters for ISPF Applications Specify operational options and terminal display attributes

    3. SAS Global Parameters for ISPF Applications Specify SAS library data set names and SAS options

    4. Data Set Allocation Parameters Specify parameters used to allocate ISPF application data sets

    5. MICS Data Set Name Table Specify non-standard MICS data set names.

    Note: Please select all of the options and perform the parameter data entry. The site definition table was not found which indicates that this is the first invocation of MWF.
    ---------------------------------------------------------------------

  2. Select EACH of the parameter initialization options listed on your version of the MICS Administrator Facility Parameter panel and supply the new sharedprefix, prefix, or PROCLIB data set names as appropriate. If you need additional information about these parameters, use the HELP command (PFK 1/PFK13) for each panel. After you have selected all of the options and supplied the default values the primary MICS Workstation Facility (MWF) panel will be displayed.

  3. Review the default data set names that are allocated in MICF and MSAS (Options 2 and 3 on the MWF primary options panel). Correct the
    data set name suffixes to meet your installation's requirements, if required.

Step 5. Change any System Administrator report programs or shared or private MICF inquiries, and MICF batch reporting jobstreams to specify the
new sharedprefix, prefix, procedure library or tapeprefix as required.

SECTION D. UPDATING THE COMPLEX LEVEL PARAMETERS AND JCL

 *************************************************************
 *  Complete this entire section if you are changing the     *
 *  MICS sharedprefix name.  Complete steps 6, 7 and 11 - 14 *
 *  if you are only changing the PROCLIB name.               *
 *************************************************************

Step 6. Edit the new sharedprefix.MICS.PARMS(JCLDEFC) as follows:

  1. Change the SHAREDPREFIX keyword statement to reflect the new sharedprefix name.

  2. If you are changing the procedure library name, update the PROCLIB keyword statement.

Step 7. Edit the new sharedprefix.MICS.PARMS(USERJCL) as follows:

  1. Change the old sharedprefix references to the new sharedprefix name.

  2. If you have changed the PROCLIB name, code the appropriate PROCLIB data set name.

Step 8. Edit the new sharedprefix.MICS.PARMS(JCLNAMES). Change the old sharedprefix references to the new sharedprefix name. If you are not sure how to use the JCLNAMES member, refer to the MICS PIOM Guide, Section 2.3.3.3.2.3 for a description of this library member.

Step 9. Edit the new sharedprefix.MICS.GENLIB(DBTABLE) so that it contains a single line beginning in column 1 that reads: *::

*************************************************************
* NOTE: Step 10 is for MICS4 sites only                     *
*************************************************************

Step 10. Edit the new sharedprefix.MICS.CNTL(JCLGEN$) and change the old sharedprefix references to the new sharedprefix name.

  1. Submit the new sharedprefix.MICS.CNTL(JCLGEN$). Ensure that the job completes with a condition code of zero.

Step 11. Submit the new sharedprefix.MICS.CNTL(JCLGEN0). Ensure that there are no error messages in the MICSLOG, that the last message is BAS10999I (the normal termination message), and that the job completes with a condition code of zero.

Step 12. Submit new sharedprefix.MICS.CNTL(PROCJOB1). Ensure that the job completes with a condition code of zero.

Step 13. If MICS Accounting and Chargeback is installed, submit the new sharedprefix.MICS.CNTL(JCLGEN1). Ensure that there are no error messages in the MICSLOG, that the last message is BAS10999I (the normal termination message), and that the job completes with a condition code of zero.

Step 14. If I/S Management Alert is installed, submit the new sharedprefix.MICS.CNTL(JCLGEN2). Ensure that there are no error messages in the MICSLOG, that the last message is BAS10999I (the normal termination message), and that the job completes with a condition code of zero.

SECTION E. UPDATING THE UNIT LEVEL PARAMETERS AND JCL

 *************************************************************
 *                                                           *
 *  If you are changing both the sharedprefix and the unit   *
 *  level prefix complete steps 15 - 21 in this section,     *
 *  then proceed to section G in this checklist.             *
 *                                                           *
 *  If you are changing only the sharedprefix name complete  *
 *  steps 19 and 20 in this section for EVERY unit in the    *
 *  complex, then proceed to section G in this checklist.    *
 *                                                           *
 *  If you are changing only the unit level prefix complete  *
 *  steps 15-21 in this section, then proceed to section G   *
 *  in this checklist.                                       *
 *                                                           *
 *  If you are changing only the unit's tapeprefix complete  *
 *  steps 15 and 20 in this section, then proceed to section *
 *  F in this checklist.                                     *
 *                                                           *
 *  If you are changing only the procedure library           *
 *  (PROCLIB) name complete steps 15, 16, 20, and 21 for     *
 *  EVERY unit in the complex, then proceed to section G in  *
 *  this checklist.                                          *
 *************************************************************

Step 15. Edit prefix.MICS.PARMS(JCLDEF) as follows:

  1. If you are changing the data base unit's prefix, update the PREFIX keyword statement to reflect the new prefix name.

  2. If you are changing the high level qualifier of your unit level tape data sets, also change the TAPEPREFIX keyword statement. Write down the old tapeprefix name for use in section F of this checklist and ensure that a new GDG catalog entry is created for the new tapeprefix.

  3. If you are changing the name of your JCL procedure library (PROCLIB), enter the new name on the PROCLIB keyword statement.

Step 16. Review the following members in the prefix.MICS.PARMS library. Change any old prefix references to the new prefix name in each member:

 INPUTccc
 IMSSPND                (if IMS is installed)
 JCLNAMES               (if user-defined DSNs)
 USERJCL                (if user-defined JCL)

where ccc is the MICS product identifier.

  1. If you are changing the name of your JCL procedure library, change the PROCLIB statement in USERJCL to specify the correct library name.

Step 17. If you are changing the prefix of the unit delete prefix.MICS.USER.SOURCE(PREFIX).

Step 18. If you are changing the prefix of the unit edit the prefix.MICS.CHECKPT.DATA. Change the prefix name defined on the first line in column 164 through column 185 to the new prefix. Ensure that your ISPF EDIT profile has the NUMBER OFF option in effect, as this data set should not have line numbers.

*************************************************************
*  NOTE:  For steps 19 and 20 JCLGENA applies to MICS4      *
*         sites only.                                       *
*************************************************************

Step 19. Change the prefix.MICS.CNTL(JCLGENA) member to reflect the new sharedprefix and/or prefix names.

Step 20. Submit the following jobs in the order listed; ensure that each job completes successfully. If MICSLOG is present, ensure that it does not contain any error messages.

Note: the GDGSGEN job can be skipped if you did not change the tapeprefix in this unit.

 prefix.MICS.CNTL(JCLGENA)
 prefix.MICS.CNTL(JCLGENB)
 prefix.MICS.CNTL(PROCJOB2)
 prefix.MICS.CNTL(JCLGENC)
 prefix.MICS.CNTL(PROCJOB3)
 prefix.MICS.CNTL(JCLGEND)
 prefix.MICS.CNTL(GDGSGEN)

Step 21. If this is a SPECIAL unit data base, submit prefix.MICS.CNTL(JCLGENF). Ensure that the job completes with a condition code of zero and that there are no error messages in MICSLOG.

 *************************************************************
 *  Repeat this section for all units if you are changing    *
 *  the MICS sharedprefix or PROCLIB name.                   *
 *************************************************************

SECTION F. COPYING THE UNIT-LEVEL TAPE FILES

*************************************************************
 *  If you are changing the unit level tapeprefix review     *
 *  steps 22 - 28 and execute the applicable steps;          *
 *  otherwise skip to Section G.                             *
 *************************************************************

The oldtapeprefix data sets cannot be changed by simply renaming the data set - the internal tape label will still carry the oldtapeprefix name. Therefore, you must physically copy the unit level tape data sets to a new tape as follows:

Step 22. If the MICS Accounting and Chargeback product is installed:

  1. Edit prefix.MICS.CNTL(ACTINITA). Change the SYSUT1 DD statement so that it states:

    //SYSUT1 DD DISP=OLD,
    DSN=oldtapeprefix.MICS.ACCT.DAY2(0)

    This job will copy the backup version of the month-to-date accounting audit tape to the new tapeprefix data set name.

  2. Submit the job and ensure that it completes with a condition code of zero.

  3. Change the SYSUT1 DD statement back to state: //SYSUT1 DD DUMMY,DCB=BLKSIZE=4096

Step 23. If the MICS Accounting and Chargeback product is installed, consider copying the existing monthly accounting audit data sets, named oldtapeprefix.MICS.ACCT.MONTH.GnnnnV00. To the newtapeprefix. The monthly accounting tapes are not needed for processing but do contain a month's worth of journal data. These tapes could come in handy for reporting purposes or ledger file recreation.

  1. If you choose NOT to copy these tape files, skip to step 24. Inform your users that the monthly accounting audit tapes that were created prior to the change will remain under the oldtapeprefix name. Another option is to manually uncatalog the oldtapeprefix files after month-end processing and reporting has been completed. ISPF option 3.4 may be used for this purpose.

  2. If you choose to copy the monthly accounting audit tapes, use one of the following two methods:

    If you choose to copy only the current GDG level of the file, create a jobstream using the following sample JCL:
    //jobname  JOB  ....
    //         EXEC PGM=IEBGENER,REGION=512K
    //SYSIN    DD   DUMMY
    //SYSPRINT DD   SYSOUT=*
    //SYSUT1   DD   DISP=OLD,UNIT=tapeunit,
    //  DSN=oldtapeprefix.MICS.ACCT.MONTH(0)
    //SYSUT2   DD   DISP=(NEW,CATLG,DELETE),
    //  UNIT=tapeunit,
    //  DSN=newtapeprefix.MICS.ACCT.MONTH(+1)
    
    where tapeunit is the tape device name. If you choose to copy ALL GDG levels create a jobstream using the following JCL as an example. Add as many steps as required to copy all of the GDG levels.
    //jobname  JOB  ....
    //STEP1    EXEC PGM=IEBGENER,REGION=512K
    //SYSIN    DD   DUMMY
    //SYSPRINT DD   SYSOUT=*
    //SYSUT1   DD   DISP=OLD,UNIT=tapeunit,
    //  DSN=oldtapeprefix.MICS.ACCT.MONTH(-9)
    //SYSUT2   DD   DISP=(NEW,CATLG,DELETE),
    //  UNIT=tapeunit,
    //  DSN=newtapeprefix.MICS.ACCT.MONTH(+1)
    //*
    //STEP2    EXEC PGM=IEBGENER,REGION=512K
    //SYSIN    DD   DUMMY
    //SYSPRINT DD   SYSOUT=*
    //SYSUT1   DD   DISP=OLD,UNIT=tapeunit,
    //  DSN=oldtapeprefix.MICS.ACCT.MONTH(-8)
    //SYSUT2   DD   DISP=(NEW,CATLG,DELETE),
    //  UNIT=tapeunit,
    //  DSN=newtapeprefix.MICS.ACCT.MONTH(+2)
    where tapeunit is the tape device name. Start with the oldest GDG level as input on the SYSUT1 DD statement in STEP1 and work your way up to the current (0) level in the subsequent steps. Specify the GDG levels on the SYSUT2 DD statements of each step in ascending order (+1, +2, +3). This specification will retain the creation order of the tape data sets by selecting the oldest GDG first and then proceeding until the (0) level is copied. For example, if the maximum number of GDG levels for oldtapeprefix.ACCT.MONTH is 10, start with -9 on the SYSUT1 DD statement and +1 on the SYSUT2 DD statement in STEP1. In STEP2 specify -8 on SYSUT1 and +2 on SYSUT2. Continue in this manner until the last step, where SYSUT1 is 0 and SYSUT2 is +10.

  3. Submit the job that you have coded and ensure that it completes with a condition code of zero.

Review steps 24 - 26 of the checklist if YES is specified for audit, weekly, or monthly archiving in the JCLDEF member of prefix.MICS.PARMS; otherwise, skip to step 27.

Step 24. If weekly history archive is active in the this unit:

  1. Create prefix.MICS.CNTL(WEEKLYX). Copy in the JCL of the prefix.MICS.CNTL(WEEKLY) member.

  2. Modify the DD statements in the WEEKLYX member that begin with "//HIiiifff" in the WEEK300 step, where iii is the information area and fff is the file name. Change the DSN parameter to the oldtapeprefix.HISTW.iiifff(0) name. The WEEKLYX job should be used for only the FIRST execution of the weekly job in the newprefix unit. EXECUTION OF THIS JOB AFTER THE FIRST WEEK WILL RESULT IN A LOSS OF DATA! Make sure that the normal WEEKLY job is executed in subsequent weeks.

Step 25. If monthly history archive is active in the prefix unit:

  1. Create prefix.MICS.CNTL(MONTHLYX). Copy in the JCL of the prefix.MICS.CNTL(MONTHLY) member.

  2. Modify the DD statements in the MONTHLYX member that begin with "//HIiiifff" in the MONTH300 step, where iii is the information area and fff is the file name. Change the DSN parameter to the oldtapeprefix.HISTM.iiifff(0) name. The MONTHLYX job should be used for only the FIRST execution of the monthly job in the newprefix unit. EXECUTION OF THIS JOB AFTER THE FIRST MONTH WILL RESULT IN A LOSS OF DATA! Make sure that the normal MONTHLY job is executed in subsequent months.

Step 26. If audit archiving is performed in WEEK300:

  1. Consider copying the weekly audit tapes, named oldtapeprefix.MICS.AUDIT.iiifff.GnnnnV00, to the new tapeprefix. Review section 9.3 in the System Modification Guide for more information on copying MICS audit archive tape files.

  2. If you choose NOT to copy these tape files inform your users that audit archive tapes that were created prior to the changes will remain under the oldtapeprefix name. Another option is to manually uncatalog the tapes. ISPF option 3.4 may be used for this purpose.

Step 27. Submit prefix.MICS.CNTL(BACKUP) to create a current backup of the unit level data files under the new tapeprefix.

Step 28. Do not complete the following steps until the disposition of any audit archive files has been determined and the WEEKLYX and MONTHLYX jobs have completed in this unit:

  1. Uncatalog the oldtapeprefix audit and weekly/monthly history archive data set names from the system catalog. You may also want to uncatalog these tapes in your tape management system.

  2. Delete the oldtapeprefix GDG base entries for each product's audit, and weekly/monthly history tape files as applicable.

SECTION G. FINALIZING THE PROCESS

Step 29. If the sharedprefix or prefix name was changed, create a suitable backup copy of all new sharedprefix and prefix MICS system libraries (e.g., CNTL, PARMS, USER.SOURCE).

Step 30. Review your security requirements for the complex. You may want to consider data set security as well as authorization levels in MWF. Refer to Chapter 4 of the Planning, Installation, Operation, and Maintenance Guide (PIOM) for more information on authorization levels in MWF.

Step 31. Copy regenerated MICS operational jobs and/or procedures to production libraries if applicable.

********************************************************
*  Reactivate production processing in each unit.      *
********************************************************

Step 32. Notify MICS users that your changes have been completed and that MWF is once again active. This completes the checklist for changing the sharedprefix, prefix, tapeprefix or procedure library name for MICS. *EndFIX