5. Maintenance › 5.4 Convert CA MICS to a New SAS Version › 5.4.2 Converting to a New SAS Version Checklist
5.4.2 Converting to a New SAS Version Checklist
*************************************************************
* *
* WARNING! This procedure converts your entire CA MICS *
* complex and all database units to a new version *
* of SAS. You CANNOT operate your CA MICS *
* complex with mixed versions of SAS. *
* *
* If you are using CA MICS Q&R Workstation (Q&R), *
* execute a separate instance of the CA MICS *
* Mainframe Server for each unique SAS version, *
* OR verify that you have applied any product *
* changes in support of the new SAS version to *
* ALL the CA MICS complexes that the Mainframe *
* Server accesses. *
* *
* If you have any questions or concerns, contact *
* Technical Support before beginning this *
* procedure. *
* *
*************************************************************
This section provides a procedure for updating CA MICS when
you upgrade to a new SAS version. This procedure must be
completed even if your SAS System Library names are the same
as your previous SAS System Library names.
*************************************************************
* *
* Note: This procedure only applies to a new SAS version, *
* for example, for upgrading from SAS version 9.1.3 *
* to SAS 9.2. *
* *
* Do NOT use this procedure to upgrade to a new *
* maintenance release of your SAS system, for *
* example, upgrading from SAS 9.1.3 TS-1 to TS-2. *
* For such maintenance upgrades, see section 5.3. *
* *
*************************************************************
__ 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.
Note: See the CA MICS Q&R Workstation Administration
Guide for general information about stopping the
Q&R Mainframe Server.
__ 2. Apply CA MICS Product Changes
Apply the CA MICS product changes that provide support
for the new SAS version.
For assistance, contact Technical Support.
__ 3. Back up Existing CA MICS SAS Libraries
Back up your existing CA MICS SAS libraries. If you
plan to use the same libraries for the new SAS version
that you use for the current SAS version, we recommend
that you make a backup copy of your current SAS
libraries before proceeding.
__ 4. (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 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 saspfx to the data set qualifier of the
new SAS libraries.
__ Change micssaspfx 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. Uncomment the statement with the
disposition (DISP=) parameter that reflects the
status of your output data sets.
//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
//OSASAUTO 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.ENW0.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
//*SYSUT2 DD DISP=(,CATLG),
//* LIKE=saspfx.ENW0.SASHELP
//SYSIN DD DUMMY
__ Submit the job and verify that it finishes with a
return code of 0.
__ 5. (CONDITIONAL) Conversion to SAS 9.1.3 ONLY
If you are converting to SAS 9.1.3, the SAS Autocall
library (sasprefix.W0.AUTOLIB) must be converted to a
fixed block data set to address issues documented in
SAS Usage Note SN-013990. Review this SAS Usage Note
before proceeding with the rest of this conversion
checklist.
This data set should be used only for CA MICS, and is
only necessary for SAS 9.1.3. The fixed-block version
of the SAS Autocall library must be created with an
LRECL of 80 and a BLKSIZE that is a multiple of 80.
Note that standard IBM utilities, such as IEBCOPY,
will not copy variable blocked data sets to fixed
block.
The following is a sample job using the SAS provided
VBGT72 macro, referenced in SN-013990 to copy the SAS
Autocall library. VBGT72 must be downloaded from the
SAS institute support site before it can be used. In
this example, VBGT72 was downloaded and then saved
as member VBGT72 in sasprefix.VBGT72.LIBRARY:
// ....JOB....
//VBGT72 EXEC SAS
//VBGT72 DD DISP=SHR,DSN=sasprefix.VBGT72.LIBRARY
//ISASAUTO DD DISP=SHR,DSN=sasprefix.W0.AUTOLIB
//AUTOOUT DD DISP=(NEW,CATLG,DELETE),
// DSN=micssasprefix.FB.W0.AUTOLIB,
// UNIT=unit,VOL=SER=volume,
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=6160),
// SPACE=(CYL,(1,1,45))
//SYSIN DD *
%INCLUDE VBGT72(VBGT72);
%VBGT72(indd=ISASAUTO);
//
The JCL will need to be modified before submission to
suit your site requirements.
Alternatively, the copy utility provided with ISPF
(Option 3.3) can be used.
*************************************************************
* *
* Note: Verify that all CA MICS production jobs have *
* completed at this point. Otherwise, do not *
* continue with this checklist. In particular, if *
* you enabled incremental update for one or more *
* products in any of the unit databases, verify that *
* the final DAILY job has completed. *
* *
*************************************************************
__ 6. Execute MICSLS1
Activate the LOAD and PARMS libraries' version-
dependent modules for the SAS version in use and
convert the sharedprefix.MICS.MCOLIB library to the
new version of SAS.
Upon successful completion of this job, your previous
SAS sharedprefix.MICS.MCOLIB library is renamed
to sharedprefix.MICS.MCOLIB.SASOLD.
__ Edit sharedprefix.MICS.CNTL(MICSLS1) and fill in
the parameters on the EXEC statement. Do not enter
parameters on the PROC statement.
******************************************************
* Note: For SAS 9.1.3 only, override the PROC *
* variable AUTOLIB to point to the fixed block *
* version of the SAS Autocall library created *
* in a previous step. *
* *
* The MICSLS1 job dynamically allocates the new *
* sharedprefix.MICS.MCOLIB data set using the *
* allocation parameters of the existing *
* sharedprefix.MICS.MCOLIB data set. If you *
* encounter problems with this allocation, for *
* example, due to site-specific allocation or *
* security requirements, you can uncomment the *
* NEWSASX DD of the COPYMCO step and define it *
* according to your requirements. *
******************************************************
__ Submit the following job:
sharedprefix.MICS.CNTL(MICSLS1)
+-------------------------------------------------+
| Reference(s): Section 3.2.5 |
+-------------------------------------------------+
All job steps must complete with a condition code
of zero.
If the job fails for some reason in the COPYMCO
step, after allocating the new
sharedprefix.MICS.MCOLIB.SAS9 library or in the
RENAME step, delete sharedprefix.MICS.MCOLIB.SASOLD
or sharedprefix.MICS.MCOLIB.SAS9, or both, before
resubmitting this job.
__ 7. Edit JCLDEFC
Edit sharedprefix.MICS.PARMS(JCLDEFC) and update the
following parameters with information that is
applicable to the new SAS version and library names.
SAS version 9.2 and higher require multiple SASCONFIGx
parameters to be specified.
SASAUTOS SASCONFIGx SASENV SASHELP SASLIB
SASMSG SASNAME
+----------------------------------------------------+
| Reference(s): Section 2.3.1.6.2 (Complex Lib Def's)|
+----------------------------------------------------+
__ 8. Edit JCLGEN0
Edit sharedprefix.MICS.CNTL(JCLGEN0), changing the
parameters on the EXEC statement for the MICSDM
in-stream cataloged procedure to reflect the MICS/SAS
library names. See the reference for a description of
the parameters.
+----------------------------------------------------+
| Reference(s): Section 3.3.2 |
+----------------------------------------------------+
__ 9. Execute JCLGEN0
Submit the following job:
sharedprefix.MICS.CNTL(JCLGEN0)
__ 10. 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)
If you maintain PROCs in a production PROCLIB, copy
these regenerated procedures to your production
PROCLIB.
__ 11. (CONDITIONAL) Remove SAS Encoding Conflicts
If you are changing the SAS encoding value (often
specified in the SASHELP data set name), then it is
necessary to avoid possible conflict between the old
and new SAS versions with respect to file indexes.
Run the following 'delete' job:
// JOB
//MICS JCLLIB ORDER=(sharedprefix.MICS.PROCLIB)
//DM EXEC MICSDM,SYSPARM=NOCOPY
//MCOLIB DD DISP=OLD,DSN=sharedprefix.MICS.MCOLIB
//SYSIN DD *
OPTIONS LS=80;
PROC DATASETS LIBRARY=MCOLIB;
DELETE ICFDBTDB ICFDBTDD ICFDBTIA ICFDSI ICFFDT
MAFDBC MAFDSN MAFSID;
//
__ 12. Execute MDBGEN
Generate the meta database by submitting the following
job:
sharedprefix.MICS.CNTL(MDBGEN)
__ 13. (CONDITIONAL) Execute JCLGEN1
Perform this step only if the CA MICS Accounting and
Chargeback Option product is installed.
Submit the following job:
sharedprefix.MICS.CNTL(JCLGEN1)
__ 14. (CONDITIONAL) Execute JCLGEN3
Perform this step only if you are using Q&R
Workstation.
Submit the following job:
sharedprefix.MICS.CNTL(JCLGEN3)
__ 15. (CONDITIONAL) Execute TMPLTJOB
Perform this step only if you are using Q&R
Workstation.
Submit the following job:
sharedprefix.MICS.CNTL(TMPLTJOB)
__ 16. (CONDITIONAL) Update User-defined PROTOLIB
Template members
Perform this step only if you are using Q&R
Workstation.
If you have created your own templates by creating
additional sharedprefix.MICS.PROTOLIB members, perform
the following steps:
- Edit sharedprefix.MICS.PARMS(JCLGENUC) and specify
the names of the members to be regenerated.
- Submit the following job:
'sharedprefix.MICS.CNTL(JCLGENUC)'
- Copy the regenerated members from the
sharedprefix.MICS.CNTL library to the
sharedprefix.MICS.MQR.TEMPLATE library using
ISPF 3.3.
__ 17. (CONDITIONAL) Update User-defined Templates
Perform this step only if you are using Q&R
Workstation.
If you have created your own templates by directly
copying existing templates, update these members in
the sharedprefix.MICS.MQR.TEMPLATE library, to use the
new SAS libraries.
__ 18. (OPTIONAL) Execute MICSCNVT
You can run this job to convert complex-level SAS
libraries to the new SAS version. You might or might
not be using these libraries at your installation.
sharedprefix.MICS.SCREENS
sharedprefix.MICS.MWFSAS.DATA
sharedprefix.MICS.CAPACITY
sharedprefix.MICS.CIMANAGE
sharedprefix.MICS.TABLES
Upon successful completion of this job, your original
SAS library is renamed to any.data.set.name.SASOLD,
where any.data.set.name refers to any of these data
sets.
__ Edit sharedprefix.MICS.CNTL(MICSCNVT) and fill in
the parameters on the EXEC statement. Do not enter
parameters on the PROC statement. The DATASET=
parameter specifies the fully qualified data set
name of the data set to be converted.
The MICSCNVT job dynamically allocates the new
any.data.set.name data set using the allocation
parameters of the existing any.data.set.name data
set. If you encounter problems with this
allocation, for example, due to site-specific
allocation or security requirements, or both, you
can uncomment the NEWSASX DD of the COPYMCO step
and define it according to your requirements.
__ Submit the following job:
sharedprefix.MICS.CNTL(MICSCNVT)
+----------------------------------------------------+
| Reference: Section 3.2.5 |
+----------------------------------------------------+
All job steps must complete with a condition code of
zero. However, there is a potential to get a return
code of U0999 with the following error message:
ERROR: Cannot open data library DDIN because it is
uninitialized.
This error is caused by attempting to convert an empty
data set.
If the MICSCNVT job fails in the COPYMCO step, after
allocating the new any.data.set.name.sas9 library, or
in the RENAME step, you must delete
any.data.set.name.SASOLD or any.data.set.name.SAS9, or
both, before resubmitting this job.
*************************************************************
* Repeat Steps 19 through 22 for each database unit. *
*************************************************************
__ 19. Suspend Production Operations
Note: If you enabled incremental update for one or
more products in any of the unit databases, ensure
the final DAILY job has completed.
Note: If you enabled incremental update for one or
more products in any of the unit databases, ensure
the final DAILY job has completed.
Suspend production operations for the unit database by
using the Operational Status and Tracking SUSPEND
command in MWF to deactivate production scheduling.
__ 20. (OPTIONAL) Execute MICSCNVT
Convert the prefix.MICS.MUOLIB formats library.
Upon successful completion of this job, your OLD SAS
formats library is renamed to
prefix.MICS.MUOLIB.SASOLD.
__ Edit sharedprefix.MICS.CNTL(MICSCNVT) and fill in
the parameters on the EXEC statement. Do not enter
parameters on the PROC statement. The DATASET=
parameter specifies the fully qualified data set
name of your prefix.MICS.MUOLIB data set to be
converted.
The MICSCNVT job dynamically allocates the new
any.data.set.name data set using the allocation
parameters of the existing prefix.MICS.MUOLIB data
set. If you encounter problems with this
allocation, for example, due to site-specific
allocation or security requirements, or both, you
can uncomment the NEWSASX DD of the COPYMCO step
and define it according to your requirements.
__ Submit the following job:
'sharedprefix.MICS.CNTL(MICSCNVT)'
+--------------------------------------------------+
| Reference Section 3.2.5 |
+--------------------------------------------------+
All job steps must complete with a condition code of
zero.
If the job fails for some reason in the COPYMCO
step, after allocating the new
prefix.MICS.MUOLIB.SAS9 library or in the RENAME
step, then delete the prefix.MICS.MUOLIB.SASOLD or
the prefix.MICS.MUOLIB.SAS9 library, or both, before
resubmitting the above job.
__ 21. (Optional) Convert Database Files
Convert Database Files - DETAIL DAYS WEEKS MONTHS
YEARS
__ Submit the following job to back up all your unit-
level database files.
prefix.MICS.CNTL(BACKUP)
__ Delete all your unit-level database files.
__ (CONDITIONAL) If you enabled incremental update for
one or more products in this unit database, then
delete the incremental update database and
checkpoint files.
prefix.MICS.ccc.IUCKPT
prefix.MICS.ccc.IUDETAIL
prefix.MICS.ccc.IUDAYS
__ Submit the following job to allocate all your unit-
level database files.
prefix.MICS.CNTL(ALLOCATE)
__ (CONDITIONAL) If you enabled incremental update for
one or more products in this unit database, then
submit the following job to allocate and initialize
the incremental update database and checkpoint
files:
prefix.MICS.CNTL(cccIUALC)
__ Submit the following job to restore your backed-up
database files:
prefix.MICS.CNTL(RESTORE)
__ 22. Resume Unit Operations
If you suspended the unit using Operational Status
and Tracking, you must use the RESUME command to
continue.
*************************************************************
* Repeat Steps 19 through 22 for each database unit. *
*************************************************************
__ 23. (CONDITIONAL) Start the Q&R Mainframe Server
If you are using the CA MICS Q&R Mainframe Server
with this complex, restart the server.
__ 24. (CONDITIONAL) Review References to MWF CLIST
If the name of the CA MICS SAS load library has
changed, review the section that describes the
CA MICS Workstation Facility (MWF) startup CLIST.
+----------------------------------------------------+
| Reference Section 3.3.6.2 |
+----------------------------------------------------+
__ 25. Review Instructions on Updating MWF
Review the instructions on updating MWF with the new
SAS version's parameter and data set name information.
Note: It is critical that you specify the correct SAS
version on the SAS Global Parameters for ISPF
Applications (MWF;5;0;3) panel.
+----------------------------------------------------+
| Reference(s): Section 4.4.2.3 |
+----------------------------------------------------+
__ 26. (OPTIONAL) Execute MICSCPVT
Inform all your MICF users to convert their private
SAS catalogs by following the instructions that
follow.
Each MICF user might have one or more of the following
private SAS catalogs to be converted.
userid.MICS6.USER.DATA
userid.MICS6.USER.SAS.PROFILE
userid.MICS6.USER.CAPACITY
Note: Make the sharedprefix.MICS.CNTL(MICSCPVT) job
stream available to your users so that they can
execute it to convert their private SAS catalogs.
Upon successful completion of this job, the original
SAS catalogs are renamed by adding a .SASOLD
suffix to the original data set name.
__ Edit sharedprefix.MICS.CNTL(MICSCPVT) and,
optionally, fill in the values for SAS macro
variables USERID and PREFIX following the //SYSIN
DD statement in the first job step, BLDEXEC.
o If you leave the USERID parameter blank, the
userid associated with the batch job is used to
construct the user data set names. The default
data set names are similar to the following:
&USERID..MICS6.USER.DATA
o If you specify the PREFIX parameter, this value
appears in front of the USERID in generated
data set names. For example:
&PREFIX..&USERID..MICS6.USER.DATA
The job dynamically allocates the user's new
private data sets and copies the original
private data sets to them. If you encounter
problems with this allocation, for example, due
to site-specific allocation or security
requirements, or both, you can uncomment the
NEWSASX DD of the COPYPVT step and define it
according to your requirements.
__ Submit the following job:
sharedprefix.MICS.CNTL(MICSCPVT)
+--------------------------------------------------+
| Reference Section 3.2.5 |
+--------------------------------------------------+
All job steps except the COPYPVT step must complete
with a condition code of zero. The COPYPVT step
might complete with a condition code of zero or 4.
If the job fails for some reason in the COPYPVT
step, after allocating the new private data sets, or
in the RENAME step, delete the new private data sets
before resubmitting this job.
Copyright © 2014 CA.
All rights reserved.
|
|