GFT210I CA FAQS ASO SECURITY IS DISABLED

Products

• FAQS - Automated Systems Operation

Issue/Introduction

Installing FAQS/ASO on a new z/VSE 6.2 system. When I try to access FAQS I get the PROFILE as a USER but it says it is not there.

Get a message in the FAQSMAIN partition

GFT210I CA FAQS ASO   SECURITY IS DISABLED

I ran INITIALIZE PW and a listing of PW shows the PROFILE is there.

 

 

Environment

Release : 5.1

Component : CA FAQS Production Control System for z/VSE

Resolution

run CAASOCNV.Z

This will convert the older database from 5.0 to 5.1 format

This is documented in the FAQSASO Install Guide Chapter 3 page 26 titled Installation Tasks 

CAASOCNV   CAASOCNV.Z
Convert CA FAQS ASO security members to the new user/profile format, for both native CA FAQS ASO and CA Top Secret security options.

 

Chapter 4 of the Install Guide page 43 - Converting CA FAQS ASO Security to the 5.1 Format

The CAASOCNV.Z member is a job stream that can be used to convert CA FAQS ASO security to the new 5.1 user id/profile format and, optionally, configure the CA Top Secret interface. The conversion must be run before you can use the online security interface. For more information about initializing security please refer to the section "Initializing Security" later in this chapter.
1. Extract the conversion JCL member CAASOCNV.Z from the installation library.
2. Modify the SETPARM parameters to specify the correct LIBRARY/SUBLIB where CA GSS and CA FAQS ASO were installed.
3. Read the comments at the start of the JCL to determine parameters you wish to use for the conversion.
4. Prepare the job for execution, which you will perform during the Initializing Security process, later in this chapter. If using CA Top Secret for security, the job must be run with CA Top Secret administrator authority, as the JCL produced will require this for execution. For more information when using CA Top Secret, see Appendix C in this manual.
The conversion jcl will generate new CA FAQS ASO user ids and security profile data based on what currently exists. The user id and model data for previous releases will no longer be used, but are not otherwise affected by this conversion.