IZ47924: UA CRASHES ON AN INVALID SOURCE STATEMENT WITH NO FILE NAME SPEC IFIED //SOURCE.FILE ''

APAR status

• Closed as program error.

Error description

• Environment: UA 6.2 and beyond
  Platform independent.
                         (Agent Builder 6.2.1)
  Problem Description:
  When using the FILE data provider to monitor a log file,  the
  Universal
  Agent (UA) crashes on startup, when an invalid "//SOURCE FILE"
  metafile
  statement  is specified, such that it does not contain a file
  name. For
  example: //SOURCE.FILE ''  . . . This occurs on both Windows and
  UNIX
  platforms.
  
  This can also occur when creating a log file monitor agent
  through the
  Agent Builder and using  a 'not required' variable to specify
  the
  complete log file name. When the agent is configured and a file
  name is
  not specified for the variable, the agent crashes on startup.
  
  Detailed Recreation Procedure:
  Create a  file data provider with a metafile statement
  //SOURCE.FILE ''
  with just 2 single quotes (no file name).
  Restart the Universal Agent.
  On Windows: UA crashes with an application error with a  memory
  reference.
  On UNIX, the universal agent process crashes.
  
  Related Files and Output:
  KBB_RAS1=ERROR (UNIT:kum ALL) (UNIT:logmonitor ALL)
  This result in the following log entry:
  (49B57896.0739-1:kumpifsc.c,95,"KUMP_InitializeFileSpecControl")
  Decoding input file specification for NULL
  
  On UNIX, you will also see:
  (49B57896.073A-1:kraafmn.cpp,290,"kramain") Signal caught during
  LoadAgents()! Exiting server main routine.
  

Local fix

Problem summary

• When using the FILE data provider to monitor a log file, the
  Universal Agent (UA) crashes on startup when an null filename is
  specified for the MDL "//SOURCE FILE" statement.
  
  For example:  //SOURCE.FILE '' . . .
  
  This occurs on both Windows and UNIX platforms.
  
  If this occurs, you will see the following in the log file:
  
  
  (49B57896.0739-1:kumpifsc.c,95,"KUMP_InitializeFileSpecControl")
  Decoding input file specification for NULL
  
  On UNIX you will also see this error at the end of the log:
  
  (49B57896.073A-1:kraafmn.cpp,290,"kramain") Signal caught during
  LoadAgents()!  Exiting server main routine.
  
  On Windows, there will be no more activity on that thread.
  

Problem conclusion

• The code was modified to check if the file specification is
  NULL.  If so, the file specification initialization routine is
  not invoked and the following new message is printed to the RAS
  log file.
  
  "***** File Specification is NULL.  No file to monitor!"
  
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.0-TIV-ITM-FP0003
  

Temporary fix

• Specify a file name to monitor on the //SOURCE FILE statement.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  UNIVERSAL AGENT

• Fixed component ID

  5724K1000

Applicable component levels

• R620 PSY

     UP