IV93093: WHEN SETTING UP A NEW CRONTASK JMSQSEQCONSUMER INSTANCE GET ERROR

APAR status

• Closed as program error.

Error description

• Environment:
  Websphere 8553
  TPAE 7606
  Windows 6.3
  SQL server 11.0
  
  Concerns/Problem:
  When setting up a new crontask JMSQSEQCONSUMER instance get
  error.
  We created a new Sequential Outbound Queue for our client,
  however, when trying to configure a new cron task instance, the
  system throws the following error message:
  BMXAA4176E - Attribute MEMO does not exist.
  
  Steps to reproduce the issue:
  1. Go to Cron Task Setup application
  2. Open crontask, JMSQSEQCONSUMER.
  3. In Cron Task Instances section, click New Row button to add
  a new instance.
  4. Enter a instance name, set 30 sec for Schedule, Run as user
  = maxadmiin
  5. In Cron Task Parameters section, enter
  MESSAGEPROCESSOR = psdi.iface.jms.QueueToDestManagerProcessor
  QUEUENAME = jms/maximo/int/queues/sqout
  6. Save the new instance, Maximo throws the error:
  Attribute MEMO does not exist. Gather the logs from the <HOME>
  directory and determine the process or application referencing
  the invalid attribute. (BMXAA4176) More information
  
  From the FldJMSQConsumerCronParamQName.class action section,
  there is below code:
  if(!queueConfig.isInbound())
              instance.setValue("memo",
  instance.getMessage("iface", "JMSOutboundCrontask"), 2L);
  
  this code seems to cause the issue.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Maximo Users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * WHEN SETTING UP A NEW CRONTASK JMSQSEQCONSUMER INSTANCE GET  *
  * ERROR ATTRIBUTE MEMO DOES NOT EXIST                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to latest release                                    *
  ****************************************************************
  

Problem conclusion

• Able to set up a new crontask JMSQSEQCONSUMER instance
  
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Fix Pack Release 7.6.0.8
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  INTEGRATION

• Fixed component ID

  5724R46I1

Applicable component levels

• R760 PSY

     UP