A fix is available
APAR status
Closed as program error.
Error description
Sequential file mapping can be left with a setting of NONE during the run of a sequence job. This can be a problem for a Routine Activity which contains OPENSEQ/READSEQ/WRITESEQ and relies on the map specified by NLSDEFSEQMAP
Local fix
Problem summary
Sequential file mapping is temporarily set to NONE when reading DSODBConfig.cfg. When DSODBON=1 in InformationServer/Server/DSODB, an attempt is made to read a local copy of this config file in the project. If it is not found, the SET.SEQ.MAP command to restore the original map is bypassed. Sequential file mapping of NONE can be a problem in sequence jobs which use server routines containing OPENSEQ, READSEQ, and WRITESEQ statements.
Problem conclusion
Ensure the SET.SEQ.MAP command is always called to restore the saved map after reading DSODBConfig.cfg files.
Temporary fix
Set DSODBC=0 in InformationServer/Server/DSODB/DSODBConfig.cfg.
Comments
APAR Information
APAR number
JR46174
Reported component name
INFO SRVR PLATF
Reported component ID
5724Q3612
Reported release
870
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-29
Closed date
2013-04-18
Last modified date
2013-04-18
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
INFO SRVR PLATF
Fixed component ID
5724Q3612
Applicable component levels
R870 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"InfoSphere Information Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021