A fix is available
APAR status
Closed as program error.
Error description
When defining a range of LUs using the define_lu_0_to_3_range command and specifying name_attributes = USE_HEX_IN_NAME a valid and correct but unexpected configuration is produced: any name that would have an alpha character (A-F) in the suffix is split into an individual LU definition, and any name that would have only numberic characters (0-9) in the suffix is split into ranges (00-09, 10-19, 20-29, etc.). This does not cause problems, but it does increase the size and complexity of the configuration file, and for large configurations can significantly increase the time necessary to load when starting the node.
Local fix
Stop the sna software (sna stop). Edit the sna_node.cfg file to manually code the define_lu_0_to_3_range definition. Start the sna software (sna start).
Problem summary
USERS AFFECTED: All who use Hex LU name extension PROBLEM DESCRIPTION: When defining a range of LUs using the define_lu_0_to_3_range command and specifying name_attributes = USE_HEX_IN_NAME a valid and correct but unexpected configuration is produced: any name that would have an alpha character (A-F) in the suffix is split into an individual LU definition, and any name that would have only numberic characters (0-9) in the suffix is split into ranges (00-09, 10-19, 20-29, etc.). This does not cause problems, but it does increase the size and complexity of the configuration file, and for large configurations can significantly increase the time necessary to load when starting the node. PROBLEM SUMMARY: When an LU 0-3 pool of LUs is defined using hex extensions the configuration file does not store this as a single record. Instead it is broken up into multiple define_lu_0_to_3 records so making the file more difficult to maintain. Furthermore when the LUs are queried they are sorted in order of the EBCDIC name where the fact that alphabetics are lexically lower than digits means that the LUs are not displayed in order of LU address.
Problem conclusion
The code has been altered to keep the configuration records together. In addition the sorting has been changed to use ASCII names so that the LUs are now in order of LU address.
Temporary fix
Comments
APAR Information
APAR number
IZ67598
Reported component name
CS AIX V6.X
Reported component ID
5765E5100
Reported release
631
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-06
Closed date
2010-01-06
Last modified date
2010-05-19
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
CS AIX V6.X
Fixed component ID
5765E5100
Applicable component levels
R631 PSY U833873
UP10/05/19 I 1000
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPQKF","label":"Communications Server for AIX"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"631","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
19 May 2010