TEMPLATE name restriction and DSNU1019I msg

Kapil Mathur

TEMPLATE name restriction and DSNU1019I msg
Hello Listers,

I am in a DB2 v8 on z/OS NFM environment ... I am confused about a
DSNU1019I message that I am getting ... I have been successfully
imagecopying tablespaces using LISTDEF & TEMPLATE keywords with a
imagecopy dataset template named SYSCOPY for the past year with no ill
effects ...

000017 OPTIONS EVENT (ITEMERROR,SKIP,WARNING,RC4)
000018
000019 TEMPLATE SYSCOPY1
000021 UNIT SYSDA
000022 DISP(NEW,CATLG,DELETE)
000023 SPACE CYL
000024 PCTPRIME 50
000025 MAXPRIME 1000
000026 DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)')
000029 MODELDCB DBAP.MODEL
000030 BUFNO 99
000031 GDGLIMIT(07)
000032
000033 LISTDEF L1
000034 INCLUDE TABLESPACE URSDDB.TS320A
000035
000036 COPY LIST L1
000037 COPYDDN(SYSCOPY1)
000038 RECOVERYDDN(SYSCOPY1)
000039 FULL YES
000043 SHRLEVEL CHANGE

... I made some minor changes to the imagecopy parameters and also changed
the template name to SYSCOP1 in all places in above JCL and the same job
failed with a DSNU1019I message ...

DSNU050I DSNUGDFL - TEMPLATE SYSCOP1 UNIT SYSDA DISP(NEW,
CATLG, DELETE) SPACE CYL PCTPRIME 50 MAXPRIME 1000
DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)') MODELDCB DBAP.MODEL
BUFNO 99 GDGLIMIT(7)
DSNU1019I DSNUGDFL - INVALID TEMPLATE NAME
SYSCOP1
DSNU050I DSNUGDFL - LISTDEF L1 INCLUDE TABLESPACE
URSDDB.TS320A

However, I can still successfully use SYSCOPY and SYSCOPY1 as valid
imagecopy output dataset "template names", even though the error message
text in the DB2 Messages Manual explicitly forbids any "template name"
starting with SYS:-

Explanation: A TEMPLATE control statement specifies an invalid TEMPLATE
name. The names UTPRINT, SORTLIB and any name starting with SORTWK or
SYS may not be used.

I need help with :-
Is our site possibly missing some DB2 maintenance/APAR that would "plug this
loophole" or is this one of those situations where IBM is just not currently
enforcing this rule in DB2 V8 and will suddenly start enforcing this rule later in
(say) DB2 9 without warning .. causing grief later, at DB2 upgrade time

Thanks in advance for your advice

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Fred Edgar

Re: TEMPLATE name restriction and DSNU1019I msg
(in response to Kapil Mathur)
The message says you can't start with "SYS".

"A TEMPLATE control statement specifies an invalid TEMPLATE name. The names UTPRINT, SORTLIB and any name starting with SORTWK or SYS may not be used."

Kapil Mathur <[login to unmask email]> wrote:
Hello Listers,

I am in a DB2 v8 on z/OS NFM environment ... I am confused about a
DSNU1019I message that I am getting ... I have been successfully
imagecopying tablespaces using LISTDEF & TEMPLATE keywords with a
imagecopy dataset template named SYSCOPY for the past year with no ill
effects ...

000017 OPTIONS EVENT (ITEMERROR,SKIP,WARNING,RC4)
000018
000019 TEMPLATE SYSCOPY1
000021 UNIT SYSDA
000022 DISP(NEW,CATLG,DELETE)
000023 SPACE CYL
000024 PCTPRIME 50
000025 MAXPRIME 1000
000026 DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)')
000029 MODELDCB DBAP.MODEL
000030 BUFNO 99
000031 GDGLIMIT(07)
000032
000033 LISTDEF L1
000034 INCLUDE TABLESPACE URSDDB.TS320A
000035
000036 COPY LIST L1
000037 COPYDDN(SYSCOPY1)
000038 RECOVERYDDN(SYSCOPY1)
000039 FULL YES
000043 SHRLEVEL CHANGE

... I made some minor changes to the imagecopy parameters and also changed
the template name to SYSCOP1 in all places in above JCL and the same job
failed with a DSNU1019I message ...

DSNU050I DSNUGDFL - TEMPLATE SYSCOP1 UNIT SYSDA DISP(NEW,
CATLG, DELETE) SPACE CYL PCTPRIME 50 MAXPRIME 1000
DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)') MODELDCB DBAP.MODEL
BUFNO 99 GDGLIMIT(7)
DSNU1019I DSNUGDFL - INVALID TEMPLATE NAME
SYSCOP1
DSNU050I DSNUGDFL - LISTDEF L1 INCLUDE TABLESPACE
URSDDB.TS320A

However, I can still successfully use SYSCOPY and SYSCOPY1 as valid
imagecopy output dataset "template names", even though the error message
text in the DB2 Messages Manual explicitly forbids any "template name"
starting with SYS:-

Explanation: A TEMPLATE control statement specifies an invalid TEMPLATE
name. The names UTPRINT, SORTLIB and any name starting with SORTWK or
SYS may not be used.

I need help with :-
Is our site possibly missing some DB2 maintenance/APAR that would "plug this
loophole" or is this one of those situations where IBM is just not currently
enforcing this rule in DB2 V8 and will suddenly start enforcing this rule later in
(say) DB2 9 without warning .. causing grief later, at DB2 upgrade time

Thanks in advance for your advice

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html



______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Phil Grainger

Re: TEMPLATE name restriction and DSNU1019I msg
(in response to Fred Edgar)
In my DB2 9 messages manual DSNU1019I is listed as a Severe error (RC8 - Utility processing terminates)

Snag is, it also says that in my V8 and V7 manuals

SO, your utility ought to be failing

If it is NOT (are you sure it's performing the copy?) then you have found a bug which, when fixed, will stop your jobs working!!

Phil Grainger
CA

Hello Listers,

I am in a DB2 v8 on z/OS NFM environment ... I am confused about a
DSNU1019I message that I am getting ... I have been successfully
imagecopying tablespaces using LISTDEF & TEMPLATE keywords with a
imagecopy dataset template named SYSCOPY for the past year with no ill
effects ...

000017 OPTIONS EVENT (ITEMERROR,SKIP,WARNING,RC4)
000018
000019 TEMPLATE SYSCOPY1
000021 UNIT SYSDA
000022 DISP(NEW,CATLG,DELETE)
000023 SPACE CYL
000024 PCTPRIME 50
000025 MAXPRIME 1000
000026 DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)')
000029 MODELDCB DBAP.MODEL
000030 BUFNO 99
000031 GDGLIMIT(07)
000032
000033 LISTDEF L1
000034 INCLUDE TABLESPACE URSDDB.TS320A
000035
000036 COPY LIST L1
000037 COPYDDN(SYSCOPY1)
000038 RECOVERYDDN(SYSCOPY1)
000039 FULL YES
000043 SHRLEVEL CHANGE

... I made some minor changes to the imagecopy parameters and also changed
the template name to SYSCOP1 in all places in above JCL and the same job
failed with a DSNU1019I message ...

DSNU050I DSNUGDFL - TEMPLATE SYSCOP1 UNIT SYSDA DISP(NEW,
CATLG, DELETE) SPACE CYL PCTPRIME 50 MAXPRIME 1000
DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)') MODELDCB DBAP.MODEL
BUFNO 99 GDGLIMIT(7)
DSNU1019I DSNUGDFL - INVALID TEMPLATE NAME
SYSCOP1
DSNU050I DSNUGDFL - LISTDEF L1 INCLUDE TABLESPACE
URSDDB.TS320A

However, I can still successfully use SYSCOPY and SYSCOPY1 as valid
imagecopy output dataset "template names", even though the error message
text in the DB2 Messages Manual explicitly forbids any "template name"
starting with SYS:-

Explanation: A TEMPLATE control statement specifies an invalid TEMPLATE
name. The names UTPRINT, SORTLIB and any name starting with SORTWK or
SYS may not be used.

I need help with :-
Is our site possibly missing some DB2 maintenance/APAR that would "plug this
loophole" or is this one of those situations where IBM is just not currently
enforcing this rule in DB2 V8 and will suddenly start enforcing this rule later in
(say) DB2 9 without warning .. causing grief later, at DB2 upgrade time

Thanks in advance for your advice

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html





________________________________


IDUG 2009 - Europe * 5-9 October * Rome, Italy < http://idug.org/lseu >

IDUG.org <http://www.idug.org/> was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register here. < http://www.idug.org/component/juser/register.html >


______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Kapil Mathur

Re: TEMPLATE name restriction and DSNU1019I msg
(in response to Phil Grainger)
Phil,

Thanks for your response .. I agree with your analysis ... and I verified that I
can still use the reserved word SYSCOPY as a valid template name in a
imagecopy JCL in a DB2 v8 NFM on z/OS subsystem ... and it works ok for my
site (output below .. I verified that the imagecopy dataset contains valid data
by running a DB2 Unload utility against it and checking the output data file
created) ... since I have inadvertantly run afoul of IBM naming restrictions
(albeit with no consequences so far) , I will rename all "affected" DB2 utility
templates ... it beats the alternative of being caught unawares, the day after
an upgrade to DB2 9

DSNU000I DSNUGUTC - OUTPUT START FOR UTILITY, UTILID =
TSO1430.IMAGECP1
DSNU1044I DSNUGTIS - PROCESSING SYSIN AS
EBCDIC
DSNU050I DSNUGUTC - OPTIONS EVENT(ITEMERROR, SKIP, WARNING,
RC4)
DSNU1035I DSNUILDR - OPTIONS STATEMENT PROCESSED
SUCCESSFULLY
DSNU050I DSNUGUTC - TEMPLATE SYSCOPY UNIT SYSDA DISP(NEW,
CATLG, DELETE) SPACE CYL PCTPRIME 50 MAXPRIME 1000
DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)') MODELDCB DBAP.MODEL
BUFNO 99 GDGLIMIT(7)
DSNU1035I DSNUJTDR - TEMPLATE STATEMENT PROCESSED
SUCCESSFULLY
DSNU050I DSNUGUTC - LISTDEF L1 INCLUDE TABLESPACE
URSDDB.TS320A
DSNU1035I DSNUILDR - LISTDEF STATEMENT PROCESSED
SUCCESSFULLY
DSNU050I DSNUGUTC - COPY LIST L1 COPYDDN(SYSCOPY) FULL YES
SHRLEVEL CHANGE
DSNU1038I DSNUGDYN - DATASET ALLOCATED.
TEMPLATE=SYSCOPY
DDNAME=SYS00001
DSN=DSNT.FICLP.URSDDB.TS320A.G0004V00
DSNU400I DSNUBBID - COPY PROCESSED FOR TABLESPACE
URSDDB.TS320A
NUMBER OF PAGES=76
AVERAGE PERCENT FREE SPACE PER PAGE = 11.72
PERCENT OF CHANGED PAGES = 0.00
ELAPSED TIME=00:00:01
DSNU428I DSNUBBID - DB2 IMAGE COPY SUCCESSFUL FOR TABLESPACE
URSDDB.TS320A
DSNU010I DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN
CODE=4

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Douwe van Sluis

Re: TEMPLATE name restriction and DSNU1019I msg
(in response to Kapil Mathur)
I get the same results on a DB2 V9 NFM system.

TEMPLATE SYSCOPY works OK.
TEMPLATE SYSTEST gives DSNU1019I and util terms with RC=8.

Vriendelijke groet,
Douwe van Sluis


---- Kapil Mathur <[login to unmask email]> schrijft:

=============
Phil,

Thanks for your response .. I agree with your analysis ... and I verified that I
can still use the reserved word SYSCOPY as a valid template name in a
imagecopy JCL in a DB2 v8 NFM on z/OS subsystem ... and it works ok for my
site (output below .. I verified that the imagecopy dataset contains valid data
by running a DB2 Unload utility against it and checking the output data file
created) ... since I have inadvertantly run afoul of IBM naming restrictions
(albeit with no consequences so far) , I will rename all "affected" DB2 utility
templates ... it beats the alternative of being caught unawares, the day after
an upgrade to DB2 9

DSNU000I DSNUGUTC - OUTPUT START FOR UTILITY, UTILID =
TSO1430.IMAGECP1
DSNU1044I DSNUGTIS - PROCESSING SYSIN AS
EBCDIC
DSNU050I DSNUGUTC - OPTIONS EVENT(ITEMERROR, SKIP, WARNING,
RC4)
DSNU1035I DSNUILDR - OPTIONS STATEMENT PROCESSED
SUCCESSFULLY
DSNU050I DSNUGUTC - TEMPLATE SYSCOPY UNIT SYSDA DISP(NEW,
CATLG, DELETE) SPACE CYL PCTPRIME 50 MAXPRIME 1000
DSN('&SS..&IC.IC&LR.&PRIBAC..&DB..&TS.(+1)') MODELDCB DBAP.MODEL
BUFNO 99 GDGLIMIT(7)
DSNU1035I DSNUJTDR - TEMPLATE STATEMENT PROCESSED
SUCCESSFULLY
DSNU050I DSNUGUTC - LISTDEF L1 INCLUDE TABLESPACE
URSDDB.TS320A
DSNU1035I DSNUILDR - LISTDEF STATEMENT PROCESSED
SUCCESSFULLY
DSNU050I DSNUGUTC - COPY LIST L1 COPYDDN(SYSCOPY) FULL YES
SHRLEVEL CHANGE
DSNU1038I DSNUGDYN - DATASET ALLOCATED.
TEMPLATE=SYSCOPY
DDNAME=SYS00001
DSN=DSNT.FICLP.URSDDB.TS320A.G0004V00
DSNU400I DSNUBBID - COPY PROCESSED FOR TABLESPACE
URSDDB.TS320A
NUMBER OF PAGES=76
AVERAGE PERCENT FREE SPACE PER PAGE = 11.72
PERCENT OF CHANGED PAGES = 0.00
ELAPSED TIME=00:00:01
DSNU428I DSNUBBID - DB2 IMAGE COPY SUCCESSFUL FOR TABLESPACE
URSDDB.TS320A
DSNU010I DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN
CODE=4

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html


______________________________________________________________________

* IDUG 2009 Rome, Italy * 5-9 October * http://IDUG.ORG/Events *
______________________________________________________________________



IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html