BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.


Hi,

How to upgrade to mainframe sas 9.3 from sas 9.1.3?

Thanks in advance

Neal.

1 ACCEPTED SOLUTION

Accepted Solutions
jakarman
Barite | Level 11

Technical: 

- The Sys-programmer can install a new version on an other LPAR so it can redeployed to the others. Normally the approach is Installation/Test  Test Aceptance  Production in planned time frame with fall-backs.

   A LPAR (logical Partition) is to be seen as a virtual machine.

- You could plan a big-bang migration that is replacing the version in 1 move or with coexistance of multiple version in the goal of regression testing and stepwise migration. This choice has impact on the installation-steps.

Expection is the need for update of the SVC routines numbers and settings.  These are kernal routines like the Windows-dll updates.

- For DB/2 some additonal steps are required. RACF and SAS/connect (you are using that?) are also having some challenges.

All this is the task of your system-programmer

All docs see: Support.sas.com (Documentation for a SAS 9.3 installation in a z/OS operating environment)

The problems are:

- he will expect a SMP approach (comparable Windows MSI-package). SAS is not delivering that. They are using the softwaredepot with Java.  Running Java will require to set a hig regionsize of 800Mb. Many IT-people however are stil limites to 6 (=32Mb).     

- The approach is a Unix style installation. Sounds strange but z/Os is running a lot of that.

- When you are still using 3270 SAS interactive, there is something with the help. Scan for remote help notes in the docs.

When this all is tackled you wil get up a running SAS-environment.

Testing of SAS is commonly not in the skills of the SYS-programmer, for that a SAS specialist knowing well your environent is needed.

The configuration of SAS options should be reviewed as usual. Changes having impact on existing code to be researched. There should be no real issues, but always some minor details are popping up.

The regionsize was troublesome with 8.2 9.1.3  because of the old archaic limit been set (6Mb +32) you need probably 64M and up.

3270 terminal usage and 24*80 (hollerith card record length) are not very easy to work with compared to SAS/BI. There are also possible timing errors with I think being introduced at 9.1.3 (threaded kernal) as you are already running that  no problem.  

You could think of installing SAS/BI on mainframe (Intgration technolgies) or using SAS/connect as J.Hennessey describes.

http://support.sas.com/resources/papers/proceedings12/061-2012.pdf 

---->-- ja karman --<-----

View solution in original post

5 REPLIES 5
SASKiwi
PROC Star

You should explore the install documentation available on SAS Support:

http://support.sas.com/documentation/installcenter/93/mvs/index.html

Note there is a Migration Guide link on this page which will help you with migrating from 9.1.3 to 9.3.

jakarman
Barite | Level 11

To be added: It makes a great difference what parts need to be migrated.  

You are:

1- just using the batch environment. Possible plans to abandon mainframe.

2- still running with 3270 terminals,  using SAS/connect, Access/DB2

3- a full BI/DI environment wiht metadata involved

You have to inventarize this part. Check on the left relevant parts on migration.

As the Mainframe has the role system-programmer you should cooperarte with him and th SAS users. 

---->-- ja karman --<-----
saslovethemost
Quartz | Level 8


Thank you for your replies.

We have a batch environment where we run the daily JCLs and SAS programs update data in DB2 database. We still plan to run on 3270 terminals and have no intentions to abandon mainframe. Recently(probably an year ago) upgraded to sas9.3 in windows OS( a full BI with metadata) and want to do the same(upgrade) on mainframes MVS OS. Will it be more of( or only) system programmer side changes?, or if any development side program changes? (obviously we will be doing thorough test of the system though)? how we do sas upgrade at the mainframes side? I'm more of a windows person than the mainframes. Thanks in advance.

Neal.

jakarman
Barite | Level 11

Technical: 

- The Sys-programmer can install a new version on an other LPAR so it can redeployed to the others. Normally the approach is Installation/Test  Test Aceptance  Production in planned time frame with fall-backs.

   A LPAR (logical Partition) is to be seen as a virtual machine.

- You could plan a big-bang migration that is replacing the version in 1 move or with coexistance of multiple version in the goal of regression testing and stepwise migration. This choice has impact on the installation-steps.

Expection is the need for update of the SVC routines numbers and settings.  These are kernal routines like the Windows-dll updates.

- For DB/2 some additonal steps are required. RACF and SAS/connect (you are using that?) are also having some challenges.

All this is the task of your system-programmer

All docs see: Support.sas.com (Documentation for a SAS 9.3 installation in a z/OS operating environment)

The problems are:

- he will expect a SMP approach (comparable Windows MSI-package). SAS is not delivering that. They are using the softwaredepot with Java.  Running Java will require to set a hig regionsize of 800Mb. Many IT-people however are stil limites to 6 (=32Mb).     

- The approach is a Unix style installation. Sounds strange but z/Os is running a lot of that.

- When you are still using 3270 SAS interactive, there is something with the help. Scan for remote help notes in the docs.

When this all is tackled you wil get up a running SAS-environment.

Testing of SAS is commonly not in the skills of the SYS-programmer, for that a SAS specialist knowing well your environent is needed.

The configuration of SAS options should be reviewed as usual. Changes having impact on existing code to be researched. There should be no real issues, but always some minor details are popping up.

The regionsize was troublesome with 8.2 9.1.3  because of the old archaic limit been set (6Mb +32) you need probably 64M and up.

3270 terminal usage and 24*80 (hollerith card record length) are not very easy to work with compared to SAS/BI. There are also possible timing errors with I think being introduced at 9.1.3 (threaded kernal) as you are already running that  no problem.  

You could think of installing SAS/BI on mainframe (Intgration technolgies) or using SAS/connect as J.Hennessey describes.

http://support.sas.com/resources/papers/proceedings12/061-2012.pdf 

---->-- ja karman --<-----
saslovethemost
Quartz | Level 8

Thank you. I really appreciate your time and effort.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 2823 views
  • 3 likes
  • 3 in conversation