SYSVIEW | Security File Conversion
Article ID: 255606
Updated On:
Products
Issue/Introduction
When upgrading SYSVIEW, job INST0050 (program GSVXCNVS) combines and converts security definitions stored in member CNM4BSEC for the new release.
Environment
Release : 17.0; 16.0
Cause
The question of whether the converted security file is downward-compatible with the older SYSVIEW release. This is important when upgrading SYSVIEW on one system at a time, resulting in an environment with "mixed releases".
Resolution
Security files generated by the program GSVXCNVS are not downward compatible; when running in a mixed-release environment. In these instances, we can specify different security files using options found within the System Config. Member:
In SYSVIEW, issue the STATUS command and search for "SYSTEM CONFIG"; you'll see two matches:
System Config Member
System Config Dsn
Use these to identify the DSN and member name of your SYSVIEW configuration. Once inside the R17.0 member, add the following statement before the Logical End of File Statement:
)IF RELEASE=16.0
Dsn-System-SECURITY
)ENDIF
*. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*
* End Release Specific Options - 16.0 *
*. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*
Be sure to save the member and recycle SYSVIEW on each system to implement the changes.
Additional Information
- See the following SYSVIEW topic "HELP STATUS" for information on the STATUS command
Feedback
