PK56173: NODE AGENT FAILS TO START WITH ABEND=SDC3 U0000 REASON=000C0009 AFTER MIGRATING TO 61X.

 Fixes are available

6.1.0.15 WebSphere Application Server V6.1 Fix Pack 15 for i5/OS
6.1.0.15 WebSphere Application Server V6.1 Fix Pack 15 for AIX
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for HP-UX
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for Windows
6.1.0.17 WebSphere Application Server V6.1 Fix Pack 17 for i5/OS
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Linux
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Solaris
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for HP-UX
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Windows
6.1.0.17 WebSphere Application Server V6.1 Fix Pack 17 for AIX
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for Linux
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for Solaris
6.1.0.19 WebSphere Application Server V6.1 Fix Pack 19 for AIX
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for HP-UX
6.1.0.19 WebSphere Application Server V6.1 Fix Pack 19 for i5/OS
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Linux
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Solaris
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Windows
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server



APAR status
Closed as program error.

Error description
Running WebSphere Application Server zOS..after migrating
the Deployment manager and AppServer nodes from 51x to 61x, the
Deployment Manager starts sucessfully but the Node Agent of the
Appserver node fails to start abending with ABEND=SDC3 U0000
REASON=000C0009.

Further analysis identified that there was an extra ';'
added in the AppServer/profiles/default/properties/server.policy
file during migration which caused the NodeAgent to abend.

server.policy in 51x..
grant {
 permission java.security.AllPermission "kernel.codebase";
 permission java.security.AllPermission "java.rmi.server.
 codebase";
 permission java.util.PropertyPermission "kernel.codebase",
 "read";
 permission java.util.PropertyPermission "kernel.rfs.address",
 "read";
 permission java.util.PropertyPermission "ibm.common.log.dir",
 "read";
 permission java.lang.RuntimePermission "createClassLoader";
 permission
java.net.SocketPermission "9.12.20.220", "connect,accept,
resolve";
};

server.policy in 61x
grant {
permission java.security.AllPermission "kernel.codebase";
permission java.security.AllPermission "java.rmi.server.
codebase";
permission java.util.PropertyPermission "kernel.codebase",
"read";
permission java.util.PropertyPermission "kernel.rfs.address",
"read";
permission java.util.PropertyPermission "ibm.common.log.dir",
read";
permission java.lang.RuntimePermission "createClassLoader";
permission
java.net.SocketPermission "9.12.20.220", "connect,accept,
resolve";
   ;
};


Node Agent joblog fails to start with ..

09.30.07 S0020825  BBOO0003E WEBSPHERE FOR Z/OS CONTROL PROCESS
WP2AGNC ENDED ABNORMALLY,  REASON=C9C25808.

09.30.07 S0020825  BPXP018I THREAD 2BB8C13000000018, IN PROCESS
50463028, ENDED  WITHOUT BEING UNDUBBED WITH COMPLETION CODE
04DC3000, AND REASON CODE 000C0009.

09.30.08 S0020825  IEF450I WP2AGNC WP2AGNC - ABEND=SDC3 U0000
REASON=000C0009

09.30.08 S0020825  -WP2AGNC  ENDED.
Local fix
Edit the 61x AppServer/profiles/default/properties/server.policy
by removing the extra ';'.

Node Agent starts fine.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V6.1 for z/OS migrating with manually        *
*                 edited policy files.                         *
****************************************************************
* PROBLEM DESCRIPTION: Server fails to start after migration   *
*                      due to an inability to parse the        *
*                      was.policy file.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Exteraneous characters in the policy files (especially trailing
spaces after the semicolon in a grant statement) result in
blank permissions (semicolon on a line by itself) being added
to the was.policy file.  The runtime fails during the
parsing of these blank permissions.
Problem conclusion
Migration code has been updated to prevent the conversion of
exteraneous characters into blank permissions.  The extra
characters are now removed, to clean up the format of the
migrated policy file.

APAR PK56173 is currently targeted for inclusion in Service
Level (Fix Pack) 6.1.0.15 of WebSphere Application Server V6.1
for z/OS.
Temporary fix Comments
APAR information
APAR number PK56173
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 610
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2007-11-07
Closed date 2008-01-15
Last modified date 2008-04-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSN    UP
R601 PSN    UP
R610 PSY UK33923    UP08/03/13 P F803

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK56173.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK56173
IBM Group: Software Group
Modified date: Apr 1, 2008