OA59407: AIR053I PFADIR HOME= PFA INITIALIZATION FAILS AIRJCART METHODS PREDICTIVE FAILURE ANALYSIS

APAR status

• Closed as fixed if next.

Error description

• If your installation specifies the PFADIR= parameter in the
  /etc/PFA/ini and uses the same path as what is specified in the
  PFA user's RACF profile in the OMVS information's HOME
  parameter, but the ending '/' is used in only one of the
  parameters (either PFADIR= or the RACF profile's OMVS HOME
  parameter), PFA will fail to start.
  
  Note that this occurs only if the path in both specifications
  are not congruently set in regards to the trailing '/' in the
  path.
  
  For instance, the PFA user's ZFS directory resides at /u/pfa/.
  Specifying the PFADIR= in the /etc/PFA/ini file and the PFA
  user's RACF profile HOME parameter in the OMVS information
  section with either combination can cause this issue as in the
  following examples:
  
  PFADIR= /u/pfa/
  HOME(/u/pfa)
  or
  PFADIR= /u/pfa
  HOME(/u/pfa/)
  
  The problem is that the setting of these parameters, one with
  and one without the trailing slash, causes PFA initialization to
  think that two unique paths have been specified for the location
  of the PFA ZFS directory and the PFA user's HOME directory.
  When the PFADIR ovverride is specified, PFA removes any
  directory structure in the PFADIR= path.  Since the path in the
  OMVS HOME directory is effectively the same as specified in the
  PFADIR= parameter, PFA initialization removes the directories
  that will be needed for PFA to model successfully.
  
  When PFA subsequently tests modeling, it fails with the AIR053I
  message.  The AIR053I will also instruct you to look at the
  /path_to_PFA_ZFS/MESSAGE_ARRIVAL_RATE/systemName.launcher.log ,
  for more information. However, the launcher.log will not exist
  because the check directories were just removed invalidly.
  

Local fix

• BYPASS/CIRCUMVENTION:
  Change the PFADIR= parameter in the /etc/PFA/ini file and the
  HOME specification in the PFA user's RACF profile so that they
  are exactly the same with the trailing '/' either used in both
  parameters or not used in both parameters.
  
  or
  
  Do not specify a PFADIR= specification in the /etc/PFA/ini file
  if using the same directory as found in the PFA user's RACF
  profile HOME parameter.
  
  
  Add a # before PFADIR, i.e., #PFADIR=, to comment out its usage
  in the /etc/PFA/ini file.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of HBB77B0 and HBB77C0,                            *
  * exploiting the Predictive Failure                            *
  * Analysis (PFA).                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * AIR053I UNABLE TO INVOKE AIRJCART METHODS. received          *
  * during starting of PFA.                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Installation had specified PFADIR= parm in the /etc/PFA/ini
  file.
  The specified PFA directory path was the home directory of the
  PFA user with / at the end.  When PFA was started, installation
  received  AIR053I UNABLE TO INVOKE AIRJCART METHODS  and
  AIR056I VALIDATION FAILED DURING PFA INITIALIZATION messages
  and PFA failed to start. The directory was also deleted.
  

Problem conclusion

Temporary fix

Comments

• This APAR is being closed FIN with concurrence from the
  submitting customer.  This means that a fix to this APAR is
  expected to be delivered from IBM in a release (if any) to be
  available within the next 36 months.
  

APAR Information

• 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