The ABENDDC3 and reason code 04010001 indicate the following:
Attempt to find the Application Server Repository (ASR) entry for the
input specific server name failed. Reg 0 contains the return code from the
search routine. The ASR table is searched by UUIDs. In the job output if
you see the UUIDs are not set and defaulting to the "dummy" values:
BBOM0001I server_generic_short_name: WASDEVB.
BBOM0001I server_generic_uuid: ISHOULDINSERTUUIDHERE. <<=====
BBOM0001I server_specific_short_name: WSDEVB.
BBOM0001I server_specific_uuid: ISHOULDINSERTUUIDHERE2. <<=====
These UUIDs are set with a longer hex value assigned during the running
of customization job BBOWCPY2, the step that invokes bbowuuid.sh,
com/ibm/websphere/UuidGenerator/CreateUUID.
The BBOWCPY2 job runs a script that generates unique ID and substitutes
the eyecatcher ISHOULDINSERTUUIDHERE in any xml files it needs to.
When you still see eyecatchers ISHOULDINSERTUUIDHERE after running
BBOWCPY2, it is indicative that customization job BBOWCPY2 did not
complete successfully.
If this is the case, you can rerun the BBOWCPY2 job. Make sure the
Daemon and application controller regions are down before you run this
job. Once the BBOWCPY2 job runs successfully, you will also need to re-run
BBOWC2N job, which takes those modified xml files and generates was.env
file for use by daemon and application servers. Then restart the
application controller region.
One possible reason for the BBOWCPY2 job not completing successfully
could be that the SBBOLOAD library was not APF authorized. There can be
other reasons so the output of the BBOWCPY2 job needs to be examined.
|