| |
Results |
|
‘IF’ statement in panels too far to the left and will be executed even when “IF (&TCMD NE ‘+’)” is not true
|
When the “IF (&TCMD NE ‘+’)” statement is present in the panel code, all statements are aligned within the ‘IF’ statement so they only executed when the '+' is not used as first character on the command line.
|
|
|
|
SAS 'PUT' statement that is too long to execute at our shop.
|
//SYSUDUMP DD SYSOUT=* To override the defaults, the OPTIONS statement can be updated as follows: // OPTIONS='MACRO,DQUOTE,YEARCUTOFF=1960,S=0,S2=0',
|
|
|
|
CMNDB2DD does not apply templates to DROP and GRANT statements
|
CMNDB2DD does not apply the template to a DROP PROCEDURE or GRANT EXECUTE statement that is included in the member with the CREATE PROCEDURE statement . For example, if a customer creates their SPD (stored procedure definition) to contain the following statements, templating is only applied to the CREATE PROCEDURE statement. DROP PROCEDURE JUNK.STPROC99 RESTRICT;
|
|
|
|
Why does CMNDB2PL generate duplicate bind statements when using Libtype DBB for DB2 package binds?
|
I'm using library type of DBB to accomplish my DB2 package binds. Whenever CMNDB2PL executes , it generates a duplicate set of bind control, causing the package to be bound twice.
|
|
|
|
CMNDB2PL: Invalid comment in bind statements cause member to be dropped from bind list
|
Inclusion of an incorrectly formatted comment in a bind statement (format: /*ONLY_IN_DEV*/) caused the entire member to be omitted from the generated bind cards subsequently executed .
|
|
|
|
DB2 Stored Procedures - WLM Templating fails when definition statement "WLM ENVIRONMENT xxxxxxxx" follows NO
|
Program CMNDB2DD, executed during promote and install, is not templating the WLM ENVIRONMENT under the following conditions. WLM Env template is defined as DB90EN01 in DB2 Admin (producing CMNDB2DD sysin as: TGTWLMTEMPLATE=DB90EN01) The stored procedure definition in the SPQ source code is...
|
|
|
|
IMS Option - DD Statement missing in CMNSSIDN step (RC = 4)
|
Full error message is "IEC130I STG DD STATEMENT MISSING". This results in an empty &&LCT dataset being generated. Since the &&LCT dataset is empty, the link step executes and creates a member (TEMPNAM*) in the SYSLMOD dataset.
|
|
|
|
IMS ACB Build Statements not being deleted.
|
The workaround to the problem is to execute the UI command against the package and select option 2 to "Add/delete/update ACB statements ". You must delete the component from panel CMNIMACB. Otherwise it will be included in table ACBBLDTB at promote/install time.
|
|
|
|
CMNDB2DD problem processing comment statements in ZMF 8.1.1.01
|
SQLCA messages follow: DSNT408I SQLCODE = -198, ERROR: THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY DSNT418I SQLSTATE = 42617 SQLSTATE RETURN CODE
|
|
|
|
Why doesn't CMNWRITE expand all forms of COPY statements?
|
Why doesn't CMNWRITE expand all forms of COPY statements ?
|
|
|
