APAR status
Closed as canceled.
Error description
NETVIEW ACCESS SERVICES (NVAS) MVS R301, FMID HZU1301, COMPONENT 566536501 AND VM R300, FMID VVM1300, COMPONENT 568402801. THIS INFORMATIONAL APAR IS DESIGNED TO SUPPLEMENT INFORMATION FOUND IN THE NETVIEW ACCESS SERVICES INSTALLATION AND OPERATIONS GUIDE SH12-5195-3 FOR MVS, SH12-5552-2 FOR VM. THIS IS NOT TO TAKE THE PLACE OF THE GUIDE, BUT TO HOPEFULLY PROVIDE SOME ADDITIONAL INFORMATION THAT MAY BE OF HELP IN INSTALLATION OF THE RELEASE 3 OF NVAS. THIS INFORMATIONAL APAR WILL ALSO ADDRESS ITEMS TO BE REVIEWED WHEN MIGRATING FROM EARLIER NVAS RELEASE 2 TO NVAS RELEASE 3. PLEASE BE SURE TO REVIEW. 1) CODE INSTALLATION - NVAS RELEASE 3 HAS A DIFFERENT FMID THAN PREVIOUS RELEASES AND REQUIRES A COMPLETE PRODUCT CODE RE-INSTALL USING SMP. ENSURE THAT ANY HIPER PTFS ARE APPLIED AT INSTALLATION. BEFORE INSTALLATION, ORDER UPDATED PSP BUCKET AND ALSO REFER, FOR MVS, TO INFORMATIONAL APAR II04874 FOR OTHER PTF MAINTENANCE THAT WILL HELP YOU BRING NVAS TO VERY CURRENT MAINTENANCE LEVEL AT INSTALLATION TIME. 2) NVAS VSAM DATASET MIGRATION - THE RECORD SIZES OF NVAS VSAM PROFILE DATASETS - EMSSRTS, EMSSRTU, EMSPLDT, EMSGPRF, EMSALLT, EMSGAL AND EMSBROD - ARE THE SAME AS IN THE PREVIOUS RELEASE 2. HOWEVER, SOME ADDTIONAL ADMINSTRATION INFORMATION WILL BE ADDED TO THE EMSSRTS, EMSSRTU, EMSGPRF DATASETS IN FIELDS WHICH WERE PREVIOUSLY UNUSED. - THE RECORD SIZE OF THE EMSSRTG VSAM PROFILE DATASET HAS NOW BEEN EXTENDED BY 40 CHARACTERS TO ACCOMODATE ADDITIONAL INFORMATION REQUIRED FOR RELEASE 3 FUNCTIONS. YOU NEED TO RUN SUPPLIED EMSVSAM3 JCL TO CONVERT EXISTING RELEASE 2 EMSSRTG DATASET TO THE RELEASE 3 FORMAT. - BACKUP OF DATASETS - EACH INSTALLATION SHOULD CREATE A BACKUP COPY OF RELEASE 2 DATASETS IF YOU HAVE THEM TO TAPE OR DASD. SAMPLE JCL, EMSBACK1, IS PROVDIDED TO ASSIST IN THIS PURPOSE. 3) INPARM DATASET - NO CHANGE IS NEEDED FOR THE NVAS INPUT PARAMETER DATASET BETWEEN THE RELEASE 2 AND RELEASE 3 LEVELS. 4) NVAS PANELS - THE NVAS LOGON PANEL (EMSP00) AND THE APPLICATION SELECTION PANEL (EMSP01) HAVE BEEN MODIFIED TO INCLUDE SEVERAL NEW FIELDS IN RELEASE 3. IF YOU HAVE CUSTOMIZED THESE PANELS IN PREVIOUS RELEASE YOU MUST MIGRATE THOSE CHANGES TO THE NEW RELEASE 3 PANELS. NVAS RELEASE 3 WILL NOT START PROPERLY IF RELEASE 2 EMSP00 AND EMSP01 PANELS ARE USED AND ERROR MESSAGE EMS0453E WILL BE GENERATED. 5) USER EXITS - USER MODIFICATIONS TO THE RELEASE 2 EXITS SHOULD BE RE- INSTALLED WITH THE RELEASE 3 CODE. THE MAJORITY OF THE USER EXITS REMAIN UNCHANGED EXCEPT FOR THE FOLLOWING TWO EXITS WHERE NEW FIELDS FOR RELEASE 3 HAVE BEEN ADDED. A) - EMSELGNX, THE LOGON AUTHORIZATION EXIT, HAS TWO NEW FIELDS THAT HAVE BEEN ADDED. THE ADDRESS OF THE SECONDARY DATA AND ADDRESS OF WORK AREA HAVE BEEN ADDED TO THE EXIT. THESE FIELDS CAN BE USED FOR SECONDARY DATA AUTHENTICATION. B) - EMSENPME, THE ACCOUNTING EXIT, HAS SEVERAL FIELDS THAT HAVE BEEN ADDED. THESE INCLUDE APPLICATION UP OR DOWN FIELD, APPLICATION STATUS RECORD FIELD, APPLICATION LU NAME FIELD, APPLICATION STATUS CHANGE DATE AND TIME FIELDS. 6) NETVIEW ACCESS START PROCEDURE SOME CHANGES, IF RUNNING RELEASE 2 AND GOING TO RELEASE 3, MUST BE MADE TO CONVERT RELEASE 2 START PROC TO RELEASE 3. - MODIFY DD STATEMENTS TO POINT TO NVAS RELEASE 3 LOAD, PANEL AND PROFILE LIBRARIES. - CONCATENATE NETVIEW CNMLINK DATASET TO THE STEPLIB DD STATEMENT. (REQUIRED TO FORWARD ALERTS TO NETVIEW) _ CONCATENATE NPM SFNMLMD1 DATASET TO STEPLIB DD STATEMENT. (REQUIRED FOR INTERFACE TO NPM) - UPDATE REGION PARAMETER TO REFLECT NEW VIRTUAL STORAGE ESTIMATES. PAGE 29 OF NVAS INSTALL AND OPERATIONS GUIDE, SH12-5195-3 FOR MVS WILL ASSIST IN THIS. NOTE: THE NETVIEW CNMLINK LIBRARY MUST BE APF AUTHORIZED, AS ALSO FOR SFNMLMD1. THEREFORE, IF IT IS TO BE CONCATENATED TO THE STEPLIB, THEN ALL OTHER LIBRARIES THAT ARE CONCATENATED MUST ALSO BE APF AUTHORIZED. 7) OTHER CONSIDERATIONS - ADD NVAS RELEASE 3 LOAD LIBRARY NAME TO APF AUTHORIZED LIST IF: A) NETVIEW CNMLINK LIBRARY IS CONATENETED ON THE STEPLIB DD STATEMENT OR B) RACF INTERFACES ARE USED. - NO CHANGE IS NEEDED FOR THE EXISTING NVAS VTAM DEFINITIONS IF MIGRATING TO RELEASE 3 FROM RELEASE 2. THIS INFORMATIONAL APAR SHOWS ITEMS THAT SHOULD BE REVIEWED PRIOR TO INSTALLATION, ESPECIALLY IF MIGRATION FROM PREVIOUS RELEASE 2 IS BEING DONE. IF RUNNING RELEASE 2 AND RELEASE 3 CONCURRENTLY, PLEASE REVIEW THE FOLLOWING: YOU MAY RUN A PRODUCTION COPY OF RELEASE 2 AND A TEST COPY OF RELEASE 3 ON THE SAME HOST CONCURRENTLY. SOME INSTALLATION CONSIDERATION SHOULD BE LOOKED AT HOWEVER: 1) IT REQUIRES A DIFFERENT VTAM APPL NAME FOR NVAS RLEASE 3. YOU MUST ALSO MODIFY THE NAME SPECIFIED ON THE APPL CONTROL STATEMENT IN THE INITIALIZATION MEMBER OF THE INPARM DATASET. 2) USE A DIFFERENT SET OF VSAM PROFILE DATASETS FOR RELEASE 3. SHARING OF RELEASE 2 AND RELEASE 3 PROFILES IS NOT SUPPORTED. 3) DEFINE SEPERATE PSUEDO TERMIAL POOLS FOR APPLICATIONS THAT ARE ACCESSED VIA RELEASE 3. TWO COPIES OF NVAS CANNOT SHARE THE SAME PSEUDO TERMINAL POOL.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II05021
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1991-04-16
Closed date
1991-04-16
Last modified date
1991-04-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
13 December 2020