PI14411: UPDATES TO THE MAILER SAMPLE APPLICTION

Fixes are available

APAR status

Closed as program error.

Error description

Problem with the subjobs running too quickly and not allowing fo
all tests to be performed. A more efficient way of seeing result
would be a big help.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Extended Deployment      *
*                  Compute                                     *
*                  Grid 8.0 and the batch function             *
*                  of WebSphere Application Server 8.0         *
****************************************************************
* PROBLEM DESCRIPTION: Multiple problems and improvements      *
*                      needed with the Mailer sample.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Mailer sample applicatin needs a way to force a failure,
slow down subjobs, and change the table schema name through
the xJCL.  In addition, the creation of the output file name
needs to use the actual name from the xJCL.

Problem conclusion

Force failure test-
 To test the force failure property, first uncomment the
FORCE_FAILURE property in the IdentifyRecipientsStep in
the xJCL.  Then set the value to any value that you desire.
For an easy test, set the value to a value that is greater
than half of the total number of messages.  Then submit the
modified xJCL.  The job should return in the restartable state.
Checking the job logs shows where the job encoutered an error
with a message saying  &#162;&#226;&#130;&#172; &#147;Force Failure. &#162;&#226;&#130;&#172;  &#189; If the FORCE
property in the xJCL contains a value greater than half
of the total messages, a restart of the job will return with it
in the ended state.

Time wait test-
 This test is similar to the force failure test. First
you have to uncomment the TIME_WAIT property in the
SendPromotionsStep.  Then set the value to a small
value, preferable a value between 1 and 10. Then submit the
modified xJCL. You should notice a delay in the total
time it takes for the job to complete.  Depending on the value
entered for the TIME_WAIT property, the processing time of the
job will increase accordingly.  The time can be checked
by looking at the joblogs and comparing the start time stamp at
the top of the log to the time stamp at the bottom of the
completed job log.

Change in output file name-
 To test this change you can change the
AppendJobIdToFileName property value to true in both the output
stream of the IdentifyRecipientsStep and the input
stream of the SendPromotionsStep.  By changing this
value to true and running the job, you will be able to see that
the filename in the location specified in the filename
property of the xJCL contains the JobID appended twice.  By
setting the value to false, which is the updated value, you
will see the JobID is appended only once.

Table name test-
 To test this change you can change the value of the
TABLE_NAME_SCHEMA in the substitution-props of the xJCL.  This
will change the table name that is used to query the database
both to select the data and update it.  The query
is printed out in the job log and can be found by searching
for  &#162;&#226;&#130;&#172; &#147;getSQLQuery &#162;&#226;&#130;&#172;  &#189;.  This will show both the select
statements used and the update query statement.

APAR PI14411 is currently targeted for inclusion in Service
Level (Fix Pack) 8.0.0.4 of WebSphere Compute Grid 8.0.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?uid=swg27022998

Temporary fix

An interim fix is available upon request

Comments

APAR Information

APAR number
PI14411
Reported component name
WXD COMPUTE GRI
Reported component ID
5725C9301
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-25
Closed date
2014-06-11
Last modified date
2014-08-28

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
WXD COMPUTE GRI
Fixed component ID
5725C9301

Applicable component levels

R800 PSY
UP

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSFVRM","label":"WebSphere Extended Deployment Compute Grid"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0"}]

Document Information

Modified date:
28 April 2022

Tips

PI14411: UPDATES TO THE MAILER SAMPLE APPLICTION

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

R800 PSY

Document Information

Share your feedback

Need support?