PM61067: WEBSPHERE JOB MANAGER QUERY DOES NOT RETURN THE CORRECT OUTPUT FOR "!=RUNNING, STARTED" SPECIFIC QUERY

Fixes are available

APAR status

Closed as program error.

Error description

Job Manager query: "!=RUNNING, STARTED" quesry used to
list the non-running or inactive application servers does not
provide the correct output. Two values must be used because
the status of the dmgr and nodeagent is started, whereas the
status of the application servers is running.
.
A Cell System Property will be introduced to address this issue.
If the user wishes to use only one value, then they need to set
the Cell System Property to allow query of only " !=RUNNING "
value.

Local fix

CUSTOMER CAN USE JOB MGR QUERY OF " = RUNNING "
RATHER THAN " != RUNNING "

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server version 7 who make use of the Job    *
*                  Manager.                                    *
****************************************************************
* PROBLEM DESCRIPTION: queryManagedResources using status as   *
*                      Started return all the Application      *
*                      Servers regardless of their status.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
queryManagedResources using status as Started return all the
Application Servers regardless of their status.

Problem conclusion

Code is changed to handle case sensitivity in doing query of
the status.
The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25, 8.0.0.4 and 8.5.0.1. Please refer to the
recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM61067
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-23
Closed date
2012-05-11
Last modified date
2012-05-11

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM61067: WEBSPHERE JOB MANAGER QUERY DOES NOT RETURN THE CORRECT OUTPUT FOR "!=RUNNING, STARTED" SPECIFIC QUERY

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?