A fix is available
APAR status
Closed as program error.
Error description
Customer found he had to specify every jarfile on the classpath after installing CICS TS 4.1. Java 6 added a feature where you can use a wildcard (*) to specify a group of files all at once on your classpath. This improved the functionality of Java 5 and Java 1.4.2 which required you to list every jarfile you wished to use. If you specify a classpath as follows: /usr/lpp/cicsts/cics660\lib/\* or "/usr/lpp/cicsts/cics660/lib/*" The class would not be found as the asterisk was not being honored by CICS.
Local fix
no local fix available
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: ClassNotFoundException thrown as * * unable to resolve jar files added * * to the classpath using wildcards. * **************************************************************** * RECOMMENDATION: * **************************************************************** Users can specify additions to the classpath that a JVM is invoked with using the CLASSPATH_SUFFIX parameter within a JVMProfile. If using Java version 6 then it is valid to use a wildcard as part of the classpath, at the end of a directory, to indicate that all JAR files within that directory should be included as part of the classpath. CICS does not expand wildcards specified at the end of directory paths in the CLASSPATH_SUFFIX variable.
Problem conclusion
DFHSJCS has been updated to include the capability to expand directories that are specified with wildcards in the CLASSPATH_SUFFIX variable in JVM profiles to include all .jar and .JAR files held in the directory on the classpath with which the JVM is invoked.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM23570
Reported component name
CICS TS Z/OS V4
Reported component ID
5655S9700
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-30
Closed date
2010-12-01
Last modified date
2011-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK62741 UK62742
Modules/Macros
DESSJCS DFHSJCL DFHSJCS DFHSJCSH DFHSJPJP
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
R603 PSY UK62742
UP10/12/07 P F012
R600 PSN
UP
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 January 2011