APAR status
INTRAN
Error description
Info APAR Faster Migrations - NFM DSNTEP2, DSNTEP4, DSNTIAUL and DSNTIAD PTFS & Jobs. The following Info APAR lists the NFM PTFs for DSNTEP2, DSNTEP4, DSNTIAUL, DSNTIAD including the mandatory PTF level you must be at before migrating. There is also a discussion on when to rebind them and the use of NEWFUN= and new function IDAA support. . DSNTEP2/DSNTEP4 - A PL/I program that will run any SQL statement that can be prepared dynamically. It s source is shipped with DB2 so you can modify if you want. However, if you do not have a PL/I compiler, object code is also available. . The main difference between TEP2 and TEP4 is DSNTEP4, the newer of the two programs, used multi-row fetch. Other than that, the programs are identical. And why not just ship the one newer version that should perform better? Not everyone wants to use multi-row fetch all the time. . DSNTIAD - . An assembler based application that will execute an dynamic SQL statement EXCEPT the SELECT statement. . DSNTIAUL - . A great alternative to the UNLOAD utility. Not only unloads data in a form compatible with the DB2 LOAD utility, it also creates the appropriate LOAD control cards. . DSNTIAUL also let you execute an non-SELECT dynamic SQL statement. . =-------------------------------------------------------------= ........................... * PTFs for DSNTEP2 NFM V8 * . UK38606/PK63887 CL08/09/02 DB2 USERS MAY GET MSGIBM0201S WHEN COMPILING DSNTEP2 WITH ENTERPRISE PL/I. CL08/09/02 UK31821/PK50217 CL08/01/02 FOR DSNTEP2/4 SPECIFY STACK(2139728,,ANY) TO INSURE STORAGE CAN BE REQUESTED ABOVE THE LINE WHERE IT CAN BE SATISFIED . UK31378/PK46117 CL08/01/02 DSNT MESSAGE DOES NOT CONTAIN THE RIGHT NUMBERS OF ROWS AFFECTED DURING UPDATE. UK28031/PK45358 CL07/09/04 DSNTEP2/DSNTEP4 NOT PRINTING OUT SQLCA VALUES . The following PTFs/apars were closed 2007 or earlier: UK20347/PK30025 , UK19063/PK23460 , UK17727/PK21876, UK15672/PK20216 , UK56629/PM11712 , UK05522/PK07677 . o UK17727 v8/ PK21876 CL06/10/03 is > Mandatory < for V8 NFM for DSNTEP2, DSNTEP4, DSNTIAUL . ............................ * PTFs for DSNTIAUL NFM V8 * . UK50731/PK92192 CL09/11/04 pe/y INCOR COLUMN 73 IS BEING CONSIDERED AS PART OF THE INPUT TO SYSIN AND RESULTED SQLCODE104 ILLEGAL SYMBOL "0" . UK45442/PK56489 CL09/05/01 INCOR FILE NAME ERROR ON THE DYNAMIC CLUSTER SERVER TEMPLATE LOGGING AND TRACING PAGES marked PE , SUPERSEDED BY: UK50731 above. . UK44977/PK77651A CL09/05/01 DSNTIAUL ABEND S0C9-09 WITH XML COLUMNS , SUPERSEDED BY: UK50731 . UK42500/PK47534A CL09/01/02 DSNTIAUL GENERATED LOAD CONTROL STATEMENT HAS BAD OFFSETS WHEN LONG AND LOB COLUMNS ARE TRUNCATED , SUPERSEDED BY: UK50731 . Just listing ptfs and their apars, since these are from 2008 with same SUPERSEDED BY: UK50731 UK41762/ PK70207 , UK35603/PK59644 , UK26419/PK46518A UK25474/ PK38942 , UK25317/PK39512 , UK21196/PK28005A ..... there are more. . ........................... * PTFs for DSNTEP2 NFM V9 * . UI12441/PM85862 CL13/12/02 MSG DSNTEP2 ***INPUT STATEMENT LINES SHOWN WHEN DSNTESQ COPIED - WITH NON-CHARACTER IN POSITION 72. MULTIPLE LINES DISPLAYED. MODULES: DSN@EP2L , DSN@EP4L , DSNTEP2 , DSNTEP4 et.al. . UK49330/PK67782 CL09/10/02 INCORROUT SQLCODE060 DSNXISB2 ON CREATE SOURCED UDF WITH CHAR() was for V9 NFM includes Sqlcode-458 & VARGRAPHIC parameter, and others -060, -104, -604, sqlincorrout, sqlccsid. . UK73661/PM45482 CL11/12/02 follow-on to PM40117 (part 1) using IDAA (IBM DB2 Analytics Accelerator Version 2) or are using IBM Smart Analytics Optimizer Version 1. . *IDAA support V9 NFM PTFS (have some issues): and UK73647/PM51075 (pe), and UK76157 /PM56492 PE/y +fix and now SUPERSEDED BY: UK76160/PM54508 Hiper *IDAA support V10 NFM PTFS (have some issues): UK76103/PM50434, UK76104/PM50435 (pe), UK76105/PM50436 (pe), UK76106/PM50437 (pe), UK76107/PM51918 (pe), and UK79290/PM64396 PE/y +fix. o All IDAA PTFs should be Applied/Received at the same time to your SMPE to avoid any causer error messages. These IDAA PTFs add the new subsystem parameters ACCEL_LEVEL and QUERY_ACCELERATION to enable the new support. DSNTIJUZ & other DSNTEJxx required, review ++Holds. . Note: PM40117/V9 UK71068 allows DB2 to handle more than 65,535 SQL SET requests over a distributed connection. . ........................... * PTF for DSNTIAUL V9 NFM * UK49330/PK67782 CL09/08/17 SQLCODE060 FROM DSNXISB2 ON CREATE SOURCED UDF WITH CHAR() ..note same apar as above for DSNTEP2. . . . . . . ............................ * PTFs for DSNTEP2 NFM V10, V11 * UI12439 V10, UI12440 V11/PM85862 CL13/12/02 MSG DSNTEP2 ***INPUT STATEMENT LINES SHOWN WHEN DSNTESQ COPIED - WITH NON-CHARACTER IN POSITION 72. MULTIPLE LINES DISPLAYED. MODULE: DSN@EP2L , DSN@EP4L , DSNTEP2 , DSNTEP4 et.al. . * PTF for DSNTIAUL V10 NFM * UK77704/PM57734 CL12/04/24 ABEND04E RC00E7005 DSNXRRP M700 CAUSED BY SQLCA SANITY CHECK FOR FULL OUTER JOIN . UK54869/PM07533 CL10/04/02 V10 NEW FUNCTION UPDATE . ............ DSNTIAD - Mixed level fixes: . UK59522 v8, UK59523 v9/PM02152 CL10/08/06 INCORROUT MISCELLENEOUS DB2 FOR Z/OS SAMPLE JOB CHANGES, DSNTEJ2U . UK38967 v9/PK67860 CL08/08/14 INCORROUT DSNTIAD RECEIVES SQLCODE -084 DUE TO INCORRECTLY PARSING 2-BYTE VALUE OF SQL STATEMENT LENGTH WHICH SHOULD BE 4-BYTE IN V9 . UK26559 v8, UK26561 v9/PK43338 CL07/06/26 INCORROUT CREATE TRIGGERS JOB END WITH RC00 EVEN IF SOME TRIGGERS ARE NOT CREATED BECAUSE OF A TIMEOUT WITH DSNTIAD . . ............ Rebind DSNTEP2, DSNTEP4, DSNTIAUL, DSNTIAD at whatever your current levels are at on V10 CM8 --> these generally point to previous maint level in Vx NFM. If you are seeing V7 instead of V8 NFM PTFs levels, please review your maintenance and last bound level. You may feel these applications are running fine and they are the <same> level as your other 'working' subsystems. Using the IVP jobs DSNTEJ2x to bind is considered Optional in V10 NFM. You will only get the level of Bound Maintenance and their fixes or enhancements. . A customer may elect to run DSNTEJ2A in compat mode with a NEWFUN=(V8) or (V9) or (V10) value since the NO, YES values have been deprecated in V10. If using V8 or V9, ensure you are still that release level's SDSNLOAD. If using V10, ensure you are still pointing to the current V10 SDSNLOAD. If you make a mistake on the NEWFUN=(Vn) value, just rerun with the correct (Vn) as it only deals with the precompiler.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II14696
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-09
Closed date
Last modified date
2013-12-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
03 December 2013