5. Maintenance › 5.3 Update CA MICS for SAS System Changes
5.3 Update CA MICS for SAS System Changes
************************************************************
* Note: If you are upgrading your CA MICS system to *
* a new version of SAS, follow the instructions *
* outlined in section 5.4. *
* *
* This checklist is ONLY used for changing the *
* SAS System Library names, typically associated *
* with application of SAS System maintenance. *
* *
************************************************************
This section provides a procedure for updating CA MICS when
you change SAS System library names. Typically, library
names change to comply with data set naming standards or when
a new service pack (TSLEVEL) of SAS has been installed at
your site.
__ 1. (CONDITIONAL) Stop the Q&R Mainframe Server
If you are using the CA MICS Q&R Mainframe Server
with this complex, you must stop the server.
See the CA MICS Q&R Workstation Administrator
Guide for general information about stopping the
Q&R Mainframe Server.
__ 2. (OPTIONAL) Create CA MICS SAS Libraries
Create CA MICS SAS libraries. You can reference your
site SAS libraries, and skip this step.
+----------------------------------------------------+
| Reference(s): Section 3.3.1 (SAS Libraries) |
+----------------------------------------------------+
We recommend that you maintain one set of CA MICS SAS
libraries with SAS version-independent data set names.
When a new SAS version has been thoroughly tested at
your installation, rename your CURRENT CA MICS
production SAS libraries to a name that can identify
the release if necessary, and rename the NEW CA MICS
SAS libraries to the production data set names
currently in use.
Using version-independent data set names with CA MICS
avoids changes to CA MICS JCL and PROCs and simplifies
the upgrade to a CA MICS supported SAS version.
For example:
Current CA MICS production New SAS installation
SAS libraries: libraries:
SYS2.SAS.LIBRARY SYS2.SAS94.LIBRARY
SYS2.SAS.CONFIG SYS2.SAS94.CONFIG
SYS2.SAS.TKMVSENV SYS2.SAS94.TKMVSENV
SYS2.SAS.W0.AUTOLIB SYS2.SAS94.W0.AUTOLIB
SYS2.SAS.ENW0.SASMSG SYS2.SAS94.ENW0.SASMSG
SYS2.SAS.ENW0.SASHELP SYS2.SAS94.ENW0.SASHELP
Now that you are ready to use the new SAS version with
CA MICS, rename your current CA MICS production SAS
libraries from:
SYS2.SAS.LIBRARY
SYS2.SAS.CONFIG
SYS2.SAS.TKMVSENV
SYS2.SAS.W0.AUTOLIB
SYS2.SAS.ENW0.SASMSG
SYS2.SAS.ENW0.SASHELP
TO:
SYS2.SASvnn.LIBRARY
SYS2.SASvnn.CONFIG
SYS2.SASvnn.TKMVSENV
SYS2.SASvnn.W0.AUTOLIB
SYS2.SASvnn.ENW0.SASMSG
SYS2.SASvnn.ENW0.SASHELP
Substituting vnn for the SAS version of these
libraries if desired.
Rename the new SAS version libraries to be used for CA
MICS from:
SYS2.SAS94.LIBRARY
SYS2.SAS94.CONFIG
SYS2.SAS94.TKMVSENV
SYS2.SAS94.W0.AUTOLIB
SYS2.SAS94.ENW0.SASMSG
SYS2.SAS94.ENW0.SASHELP
to the CA MICS production SAS library names currently
in use:
SYS2.SAS.LIBRARY
SYS2.SAS.CONFIG
SYS2.SAS.TKMVSENV
SYS2.SAS.W0.AUTOLIB
SYS2.SAS.ENW0.SASMSG
SYS2.SAS.ENW0.SASHELP
With this naming convention, your CA MICS JCL should only
require changes or regeneration when a new SAS library is
added.
Modify the sample job shown here to populate the
CA MICS SAS libraries from your new SAS installation
libraries by doing the following:
__ If you are using SAS 9.2 or higher, use the
ISASCNTL and OSASCNTL DD statements with the CONFIG
data set by uncommenting them and commenting the
ones with the CNTL data set.
__ Change sasprefix to the data set qualifier of the
new SAS libraries.
Note: With SAS 9.1.3 or higher, sasprefix might
include a language and encoding abbreviation (for
example, W0 and ENW0).
__ Change micssasprefix to the data set qualifiers
that are valid for your CA MICS installation.
__ Add a JOB statement to the JCL and any installation
specific JCL.
//COPY1 EXEC PGM=IEBCOPY,REGION=2M
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//ISASENV DD DISP=SHR,DSN=saspfx.TKMVSENV
//ISASAUTO DD DISP=SHR,DSN=saspfx.W0.AUTOLIB
//ISASCNTL DD DISP=SHR,DSN=saspfx.CNTL
//*ISASCNTL DD DISP=SHR,DSN=saspfx.CONFIG
//ISASLIB DD DISP=SHR,DSN=saspfx.LIBRARY
//ISASMSG DD DISP=SHR,DSN=saspfx.ENW0.SASMSG
//*
//OSASENV DD DSN=micssaspfx.TKMVSENV,
//* DISP=OLD
//* DISP=(,CATLG),LIKE=saspfx.TKMVSENV
//OAUTOLIB DD DSN=micssaspfx.W0.AUTOLIB
//* DISP=OLD
//* DISP=(,CATLG),LIKE=saspfx.W0.AUTOLIB
//OSASCNTL DD DSN=micssaspfx.CNTL
//* DISP=OLD
//* DISP=(,CATLG),LIKE=saspfx.CNTL
//*OSASCNTL DD DSN=micssaspfx.CONFIG
//* DISP=OLD
//* DISP=(,CATLG),LIKE=saspfx.CONFIG
//OSASLIB DD DSN=micssaspfx.LIBRARY
//* DISP=OLD
//* DISP=(,CATLG),LIKE=saspfx.LIBRARY
//OSASMSG DD DSN=micssaspfx.ENW0.SASMSG
//* DISP=OLD
//* DISP=(,CATLG),LIKE=saspfx.SASMSG
//SYSIN DD *
COPY INDD=((ISASENV,R)),OUTDD=OSASENV
COPY INDD=((ISASAUTO,R)),OUTDD=OSASAUTO
COPY INDD=((ISASCNTL,R)),OUTDD=OSASCNTL
COPY INDD=((ISASLIB,R)),OUTDD=OSASLIB
COPY INDD=((ISASMSG,R)),OUTDD=OSASMSG
/*
//COPY2 EXEC PGM=IEBGENER,REGION=1M
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=saspfx.ENW0.SASHELP
//SYSUT2 DD DISP=OLD,DSN=micssaspfx.ENW0.SASHELP
//SYSIN DD DUMMY
__ Submit the job and ensure that it finishes with a
return code of 0.
__ 3. Update JCLDEFC
Review the reference for information about defining
JCLGEN parameters for SAS. Edit
sharedprefix.MICS.PARMS(JCLDEFC) and update the
following parameters with information that is
applicable to the new SAS release or library name:
SASAUTOS SASCONFIGx SASHELP SASENV
SASLIB SASMSG SASNAME
******************************************************
* Reference(s): Section 2.3.1.6.2 (JCLGEN) *
******************************************************
__ 4. Rename Libraries
Edit sharedprefix.MICS.CNTL(JCLGEN0), changing the
SASPFX= value on the EXEC statement for the MICSDM
in-stream cataloged procedure.
__ 5. Execute JCLGEN0
Submit the following job:
sharedprefix.MICS.CNTL(JCLGEN0)
Ensure that there are no error messages in SYSTSPRT or
in MICSLOG and that the last MICSLOG message is the
normal termination message, BAS10999.
__ 6. Execute PROCJOB1
The following JCL procedures changed:
MICSSDD MICSSDS
Move them to your CA MICS PROCLIB by submitting the
following job:
sharedprefix.MICS.CNTL(PROCJOB1)
Ensure that there are no error messages and that the
job completes with a condition code of zero. If you
maintain PROCs in a production PROCLIB, copy the
regenerated procedures listed to your production
PROCLIB.
__ 7. (CONDITIONAL) Execute JCLGEN3
Perform this step only if you use CA MICS
Q&R Workstation.
Submit the following job:
sharedprefix.MICS.CNTL(JCLGEN3)
Ensure that there are no error messages in SYSTSPRT or
in MICSLOG and that the last MICSLOG message is the
normal termination message, BAS10999.
__ 8. (CONDITIONAL) Execute TMPLTJOB
Perform this step only if you use CA MICS
Q&R Workstation.
Submit the following job:
sharedprefix.MICS.CNTL(TMPLTJOB)
Ensure that the job completes with a condition code 0.
__ 9. (CONDITIONAL) Start the Q&R Mainframe Server
If you are using the CA MICS Q&R Mainframe Server
with this complex, restart the server.
__ 10. (CONDITIONAL) Activate CLIST
If the name of the CA MICS SAS load library has
changed, review the reference on the CA MICS
Workstation Facility (MWF) startup CLIST.
******************************************************
* Reference: Section 3.3.6.2 *
******************************************************
__ 11. Review Instructions
Review the instructions on updating MWF with the new
SAS version's parameter and data set name information.
******************************************************
* Reference Section: 4.4.2.3 *
******************************************************
Copyright © 2014 CA.
All rights reserved.
|
|