II13298: INFO APAR FOR MERVA LIQUIDITY MANAGER WHICH HAS A COMPID OF 5799GHN00 AND A PID OF 5799GHN

APAR status

• INTRAN

Error description

• This info APAR applies to the product:
  MERVA Liquidity Manager PRPQ V110 -  PID: '5799GHN'
                                     CompID: '5799GHN00'.
  This APAR contains general information for handling of
  MERVA Liquidity Manager PRPQ problems and their classification:
  1. If the problem is on the customer's test system (as opposed
     to his production system), it should never be classified as
     a severity 1 problem, despite any plans that the customer
     might have for cutting over on any particular date.
  2. If the customer's production system is at a standstill, i.e.,
     he cannot function at all, classify the PMR as priority 1.
     If the customer is experiencing a severe loss of performance
     or function, classify as severity/priority 2.
     Otherwise, the severity/priority should be set to 3 or 4.
     If the problem results in not sending out the messages to the
     gateway circumvent the problem by bypassing LM.
  3. If the problem is NOT registered in RETAIN, a PMR should
     be opened containing a DETAILED description of the problem
     and queued to DBOB18,L245.
  Material for error diagnosis:
  a)   Problem with one of the host agents
       (see chapter 8. Analyzing problems)
       The trace output produced by the affected agent is
       required.  Set the trace parameter of the affected agent
       on.  Either use the AGTRACE runtime parameter in the DDNAME
       FMLPARM of the the agent's batch job JCL or add the entries
       in the table FML_AGTRACE with the agent name of the
       corresponding agent using SPUFI or another DB2 utility.
       Import agent:    Set the trace values II, IV, GD, LZ, LM on
       Export agent:    Set the trace values OV, GD, LZ, LM on
       Scheduler agent: Set the trace values SC, GD, LZ, LM on
       ICS agent:       Set the trace values RM, GD, LZ, LM on
       Restart the agent and reproduce the problem, save the
       output from the job log or the log file as configured in
       your installation and delete the trace entries from the
       table FML_AGTRACE.
  b)   Problem with client workstations
       (see chapter 8. Diagnosis information for client
       workstations) Set the appropriate trace (DB access trace,
       database host trace and/or programmer's trace)on, reproduce
       the problem and save the output in the corresponding trace
       file.  Set the traces off.
  Download the trace output from the host environment or save the
  output from the LM directory and put it into a ZIP file.
  Send the material to one of the following addresses:
     E-mail Address   : lmserv@de.ibm.com
     Lotus Notes Name : Worldwide LMService/Germany/IBM@IBMDE
  

Local fix

Problem summary

Problem conclusion

Temporary fix

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

Applicable component levels