Toni_Nanneman
Active Member
I received the following notice from IBM today and thought I should share...
A customer running JDE OneWorld on R440 System installed Service Pack 13.3
and ran into a major problem. To make sure that you do not run into this
problem, please check the following. (R440 is the only release effected)
The following procedures can be used to determine if SYSROUTINE and
QASQRESL match the expected 9/99 level. See steps 1, 2, and 3 below:
Note: The problem only applies to systems which had SF58102 previously
applied
1) DSPFFD QSYS2/SYSROUTINE
- If there are 35 fields, and the last field is CAST_FUNC, then the file
SYSROUTINE is at the 9/99 level.
When doing the DSPFFD; and you should see:
Display Spooled File
File . . . . . : QPDSPFFD Page/Line 1/2
Control . . . . . Columns 1 -
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+...
Number of fields . . . . . . . . . . . . . : 35 <-- This value **
Record length . . . . . . . . . . . . . . . : 29808
Field Level Information
Data Field Buffer Buffer Field Co
Page to the bottom; and you should see:
File . . . . . : QPDSPFFD Page/Line 3/57
Control . . . . . Columns 1 - 78
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
**--> CAST_FUNC CHAR 3 5 29804 Both IS_USE
Alternative name . . . . . . . . . . . . : IS_USER_DEFINED_CAST
2) DSPFFD QSYS2/QASQRESL
- If the field DATAACCESS is "Variable Length" and 17 characters, then
the file QASQRESL is at the 9/99 level.
Page down until you see this:
Allows the null value
Coded Character Set Identifier . . . . . : 37
DATAACCESS CHAR **-->17 19 873 B
Alternative name . . . . . . . . . . . . : SQL_DATA
**--> Variable length field
Allows the null value
Coded Character Set Identifier . . . . . : 37
SIGNATURE HEX 510 512 892 B
3) DSPPFM FILE(QASQSRC) MBR(QASQRESL)
Look for a row of data similar to: ... DATAACCESS 17 VARLEN
If you don't see the 17 and VARLEN, the source is back level (not
correct)
You should see something similar to:
001200000000 A DETERMINE
001300000000 A DATAACCESS 17 VARLEN
001400000000 A SIGNATURE
If all the information is correct on your system, your system will not have
this problem. Otherwise we have a few steps to fix/prevent the problem.
1) Check to see if PTF SF61907 and SF57810 are on your system in 5769SS1.
If the PTFs are not there, you will need load and apply the PTFs; and we
also recommend that you bring your system to a current cumulative PTF
level.
2) To rebuild the 'back level' source file mentioned in Step 3 above:
2.1) CALL PGM(QPZ1QQRS)
2.2) Verify the DDS Source is now correct (see steps 2 and 2.1)
3) Now to rebuild the actual files that are back level
3.1) Ensure no locks are on the files QSYS2/QASQRESL, QSYS2/SYSTYPES,
QSYS2/SYSROUTINE or QSYS2/SYSPARMS.
- If the job holding the lock is a PreStart job, then ENDPJ
or ENDSBS or ENDSYS must be used instead of ENDJOB.
- If your own job is holding the lock, then you must sign off
and then sign back on; RCLRSC typically will resolve.
3.2) DLTF QSYS2/QASQRESL
3.3) CALL QSYS/QDBFIXS2
- The above request must complete with a message indicating
success before the files are at the 9/99 level.
- If the above request fails, please give IBM Support a call
For more information on this problem, download Informational APAR II12248.
If you have any questions or comments, please respond to this note.
Technology Solution Center - ERP Team
http://www.as400.ibm.com/service/bms.htm
Toni Nanneman
CNC Administrator
503-370-7071 x7262
[email protected]
A customer running JDE OneWorld on R440 System installed Service Pack 13.3
and ran into a major problem. To make sure that you do not run into this
problem, please check the following. (R440 is the only release effected)
The following procedures can be used to determine if SYSROUTINE and
QASQRESL match the expected 9/99 level. See steps 1, 2, and 3 below:
Note: The problem only applies to systems which had SF58102 previously
applied
1) DSPFFD QSYS2/SYSROUTINE
- If there are 35 fields, and the last field is CAST_FUNC, then the file
SYSROUTINE is at the 9/99 level.
When doing the DSPFFD; and you should see:
Display Spooled File
File . . . . . : QPDSPFFD Page/Line 1/2
Control . . . . . Columns 1 -
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+...
Number of fields . . . . . . . . . . . . . : 35 <-- This value **
Record length . . . . . . . . . . . . . . . : 29808
Field Level Information
Data Field Buffer Buffer Field Co
Page to the bottom; and you should see:
File . . . . . : QPDSPFFD Page/Line 3/57
Control . . . . . Columns 1 - 78
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
**--> CAST_FUNC CHAR 3 5 29804 Both IS_USE
Alternative name . . . . . . . . . . . . : IS_USER_DEFINED_CAST
2) DSPFFD QSYS2/QASQRESL
- If the field DATAACCESS is "Variable Length" and 17 characters, then
the file QASQRESL is at the 9/99 level.
Page down until you see this:
Allows the null value
Coded Character Set Identifier . . . . . : 37
DATAACCESS CHAR **-->17 19 873 B
Alternative name . . . . . . . . . . . . : SQL_DATA
**--> Variable length field
Allows the null value
Coded Character Set Identifier . . . . . : 37
SIGNATURE HEX 510 512 892 B
3) DSPPFM FILE(QASQSRC) MBR(QASQRESL)
Look for a row of data similar to: ... DATAACCESS 17 VARLEN
If you don't see the 17 and VARLEN, the source is back level (not
correct)
You should see something similar to:
001200000000 A DETERMINE
001300000000 A DATAACCESS 17 VARLEN
001400000000 A SIGNATURE
If all the information is correct on your system, your system will not have
this problem. Otherwise we have a few steps to fix/prevent the problem.
1) Check to see if PTF SF61907 and SF57810 are on your system in 5769SS1.
If the PTFs are not there, you will need load and apply the PTFs; and we
also recommend that you bring your system to a current cumulative PTF
level.
2) To rebuild the 'back level' source file mentioned in Step 3 above:
2.1) CALL PGM(QPZ1QQRS)
2.2) Verify the DDS Source is now correct (see steps 2 and 2.1)
3) Now to rebuild the actual files that are back level
3.1) Ensure no locks are on the files QSYS2/QASQRESL, QSYS2/SYSTYPES,
QSYS2/SYSROUTINE or QSYS2/SYSPARMS.
- If the job holding the lock is a PreStart job, then ENDPJ
or ENDSBS or ENDSYS must be used instead of ENDJOB.
- If your own job is holding the lock, then you must sign off
and then sign back on; RCLRSC typically will resolve.
3.2) DLTF QSYS2/QASQRESL
3.3) CALL QSYS/QDBFIXS2
- The above request must complete with a message indicating
success before the files are at the 9/99 level.
- If the above request fails, please give IBM Support a call
For more information on this problem, download Informational APAR II12248.
If you have any questions or comments, please respond to this note.
Technology Solution Center - ERP Team
http://www.as400.ibm.com/service/bms.htm
Toni Nanneman
CNC Administrator
503-370-7071 x7262
[email protected]
