Wild card in listdef templates for copy

Avram Friedman

Wild card in listdef templates for copy

Customer is DB2 v10 CM8
I am trying to bulld an IC job that will need few modifications for V10 NFM and beyond.

This is my Guess
//SYSIN DD *
OPTIONS EVENT ( ITEMERROR, SKIP )
LISTDEF LIST1
INCLUDE TABLESPACES TABLESPACE DSNDB01.*
INCLUDE TABLESPACES TABLESPACE DSNDB06.*
EXCLUDE TABLESPACES TABLESPACE DSNDB06.SYSCOPY
TEMPLATE ICOPY
DSN(SY.DSNT.&DB..&TS..D&DT..T&TI.)
DISP (NEW,CATLG,DELETE)
UNIT VTAPE
STACK YES
BUFNO 40
RETPD 31
COPY LIST LIST1 SHRLEVEL CHANGE
COPYDDN(ICOPY)

This is what I get
DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = IMAGCOPY
DSNUGTIS - PROCESSING SYSIN AS EBCDIC
DSNUGUTC - OPTIONS EVENT(ITEMERROR, SKIP)
DSNUZODR - OPTIONS STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - LISTDEF LIST1 INCLUDE TABLESPACES TABLESPACE DSNDB01.* INCLUDE TABL
TABLESPACES TABLESPACE DSNDB06.SYSCOPY
DSNUILDR - LISTDEF STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - TEMPLATE ICOPY DSN(SY.DSNT.&DB..&TS..D&DT..T&TI.) DISP(NEW, CATLG,
0 RETPD 31
DSNUJTDR - TEMPLATE STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - COPY LIST LIST1 SHRLEVEL CHANGE COPYDDN(ICOPY)
DSNUILSA - INVALID KEYWORD SPECIFIED ON CLAUSE: INCLUDE TABLESPACE DSNDB01.%
DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8

All the IC samples I have seen in my research have each tablespace name completely spelled out.

Is this a requirement or can I get something like my hoped for method to work?

 

Avram Friedman
DB2-L hall of fame contributer
DB2-L acting administrator

[login to unmask email]

Michael Arlebrandt

SV: Wild card in listdef templates for copy
(in response to Avram Friedman)
Hi Avram,


Sorry to say that wildcarding is not supported for catalog and directory objects.


From v12 Utility manual:


Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.


best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



________________________________
Från: Avram Friedman <[login to unmask email]>
Skickat: den 23 oktober 2017 15:33
Till: [login to unmask email]
Ämne: [DB2-L] - Wild card in listdef templates for copy


Customer is DB2 v10 CM8
I am trying to bulld an IC job that will need few modifications for V10 NFM and beyond.

This is my Guess
//SYSIN DD *
OPTIONS EVENT ( ITEMERROR, SKIP )
LISTDEF LIST1
INCLUDE TABLESPACES TABLESPACE DSNDB01.*
INCLUDE TABLESPACES TABLESPACE DSNDB06.*
EXCLUDE TABLESPACES TABLESPACE DSNDB06.SYSCOPY
TEMPLATE ICOPY
DSN(SY.DSNT.&DB..&TS..D&DT..T&TI.)
DISP (NEW,CATLG,DELETE)
UNIT VTAPE
STACK YES
BUFNO 40
RETPD 31
COPY LIST LIST1 SHRLEVEL CHANGE
COPYDDN(ICOPY)

This is what I get
DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = IMAGCOPY
DSNUGTIS - PROCESSING SYSIN AS EBCDIC
DSNUGUTC - OPTIONS EVENT(ITEMERROR, SKIP)
DSNUZODR - OPTIONS STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - LISTDEF LIST1 INCLUDE TABLESPACES TABLESPACE DSNDB01.* INCLUDE TABL
TABLESPACES TABLESPACE DSNDB06.SYSCOPY
DSNUILDR - LISTDEF STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - TEMPLATE ICOPY DSN(SY.DSNT.&DB..&TS..D&DT..T&TI.) DISP(NEW, CATLG,
0 RETPD 31
DSNUJTDR - TEMPLATE STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - COPY LIST LIST1 SHRLEVEL CHANGE COPYDDN(ICOPY)
DSNUILSA - INVALID KEYWORD SPECIFIED ON CLAUSE: INCLUDE TABLESPACE DSNDB01.%
DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8


All the IC samples I have seen in my research have each tablespace name completely spelled out.

Is this a requirement or can I get something like my hoped for method to work?



Avram Friedman
DB2-L hall of fame contributer
DB2-L acting administrator

[login to unmask email]

-----End Original Message-----


::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------

Michael Arlebrandt

SV: Wild card in listdef templates for copy
(in response to Michael Arlebrandt)
And that's why we do like this...


example is V10 NFM


//* COPY JC BEFORE THIS LINE AND CHANGE JOBNAME TO D2XXICPY
//*---------------------------------------------------------------------
//* C F1D2XX YOUR_HLQ ALL
//* C D2XX YOUR_DB2 ALL
//* C 'SHRLEVEL CHANGE' REFERENCE OR CHANGE
//*---------------------------------------------------------------------
//*
//* VERSION 10 NFM AS OF 140519
//*
//* CREATE IMAGE COPIES OF ALL THE SYSTEM CATALOG TABLES
//*
//* NOTE! USE OF TEMPLATES AND PARALLEL PROCESSING
//* NOTE! SYSLGRNX AND SYSCOPY IS ALWAYS IMAGE COPIED LAST!!
//*
//*---------------------------------------------------------------------
//* COPY OF SYSUTILX HAS TO BE RUN IN A SEPARATE STEP
//*---------------------------------------------------------------------
//IMAGCOP1 EXEC PGM=DSNUTILB,PARM='D2Y2,IMAGCOP1',COND=(4,LT)
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
TEMPLATE ICPYTPLT
DSN 'F1D2XX.IC.&SSID..&TS..D&DATE..&UNIQ.'
DISP (NEW,CATLG,DELETE)
MGMTCLAS(EMID35)
PCTPRIME 100 MAXPRIME 3000 NBRSECND 10
-- OR UNIT 3490 STACK YES

COPY TABLESPACE DSNDB01.SYSUTILX COPYDDN ICPYTPLT SHRLEVEL CHANGE
/*
//*---------------------------------------------------------------------
//IMAGCOP2 EXEC PGM=DSNUTILB,PARM='D2Y2,IMAGCOP2',COND=(4,LT)
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *

TEMPLATE ICPYTPLT
DSN 'F1D2XX.IC.&SSID..&TS..D&DATE..&UNIQ.'
DISP (NEW,CATLG,DELETE)
MGMTCLAS(EMID35)
PCTPRIME 100 MAXPRIME 3000 NBRSECND 1
-- OR UNIT 3490 STACK YES

LISTDEF ICPYDB01
INCLUDE TABLESPACE DSNDB01.DBD01
INCLUDE TABLESPACE DSNDB01.SCT02
INCLUDE TABLESPACE DSNDB01.SPT01
INCLUDE TABLESPACE DSNDB01.SYSDBDXA
INCLUDE TABLESPACE DSNDB01.SYSSPUXA
INCLUDE TABLESPACE DSNDB01.SYSSPUXB

LISTDEF ICPYDB06
INCLUDE TABLESPACE DSNDB06.SYSTSFAU
INCLUDE TABLESPACE DSNDB06.SYSTSCOL
INCLUDE TABLESPACE DSNDB06.SYSTSTSP
INCLUDE TABLESPACE DSNDB06.SYSTSTPT
INCLUDE TABLESPACE DSNDB06.SYSTSTAB
INCLUDE TABLESPACE DSNDB06.SYSTSIXS
INCLUDE TABLESPACE DSNDB06.SYSTSIXT
INCLUDE TABLESPACE DSNDB06.SYSTSIXR
INCLUDE TABLESPACE DSNDB06.SYSTSIPT
INCLUDE TABLESPACE DSNDB06.SYSTSREL
INCLUDE TABLESPACE DSNDB06.SYSTSFOR
INCLUDE TABLESPACE DSNDB06.SYSTSSYN
INCLUDE TABLESPACE DSNDB06.SYSTSFLD
INCLUDE TABLESPACE DSNDB06.SYSTSTAU
INCLUDE TABLESPACE DSNDB06.SYSTSKEY
INCLUDE TABLESPACE DSNDB06.SYSTSDBA
INCLUDE TABLESPACE DSNDB06.SYSTSDBU
INCLUDE TABLESPACE DSNDB06.SYSGPAUT
INCLUDE TABLESPACE DSNDB06.SYSTSSTG
INCLUDE TABLESPACE DSNDB06.SYSTSVOL
INCLUDE TABLESPACE DSNDB06.SYSTSPLN
INCLUDE TABLESPACE DSNDB06.SYSTSPLA
INCLUDE TABLESPACE DSNDB06.SYSTSDBR
INCLUDE TABLESPACE DSNDB06.SYSTSPLD
INCLUDE TABLESPACE DSNDB06.SYSTSSTM
INCLUDE TABLESPACE DSNDB06.SYSTSPKL
INCLUDE TABLESPACE DSNDB06.SYSTSPLY
INCLUDE TABLESPACE DSNDB06.SYSTSPKG
INCLUDE TABLESPACE DSNDB06.SYSTSPKS
INCLUDE TABLESPACE DSNDB06.SYSTSPKX
INCLUDE TABLESPACE DSNDB06.SYSTSPVR
INCLUDE TABLESPACE DSNDB06.SYSTSPKY
INCLUDE TABLESPACE DSNDB06.SYSTSPKD
INCLUDE TABLESPACE DSNDB06.SYSTSPKA
INCLUDE TABLESPACE DSNDB06.SYSUSER
INCLUDE TABLESPACE DSNDB06.SYSSTR
INCLUDE TABLESPACE DSNDB06.SYSTSVEW
INCLUDE TABLESPACE DSNDB06.SYSTSVWD
INCLUDE TABLESPACE DSNDB06.SYSTSVWT
INCLUDE TABLESPACE DSNDB06.SYSTSVTR
INCLUDE TABLESPACE DSNDB06.SYSSTATS
INCLUDE TABLESPACE DSNDB06.SYSDDF
INCLUDE TABLESPACE DSNDB06.SYSTSAUX
INCLUDE TABLESPACE DSNDB06.SYSTSCON
INCLUDE TABLESPACE DSNDB06.SYSTSDAT
INCLUDE TABLESPACE DSNDB06.SYSTSDEP
INCLUDE TABLESPACE DSNDB06.SYSTSENV
INCLUDE TABLESPACE DSNDB06.SYSTSKYC
INCLUDE TABLESPACE DSNDB06.SYSTSPRM
INCLUDE TABLESPACE DSNDB06.SYSTSRAU
INCLUDE TABLESPACE DSNDB06.SYSTSROU
INCLUDE TABLESPACE DSNDB06.SYSPLUXA
INCLUDE TABLESPACE DSNDB06.SYSPLUXB
INCLUDE TABLESPACE DSNDB06.SYSTSSCM
INCLUDE TABLESPACE DSNDB06.SYSTSTBC
INCLUDE TABLESPACE DSNDB06.SYSTSTRG
INCLUDE TABLESPACE DSNDB06.SYSTSTRT
INCLUDE TABLESPACE DSNDB06.SYSSEQ
INCLUDE TABLESPACE DSNDB06.SYSSEQ2
INCLUDE TABLESPACE DSNDB06.SYSHIST
INCLUDE TABLESPACE DSNDB06.SYSGRTNS
INCLUDE TABLESPACE DSNDB06.SYSJAUXA
INCLUDE TABLESPACE DSNDB06.SYSJAUXB
INCLUDE TABLESPACE DSNDB06.SYSJAVA
INCLUDE TABLESPACE DSNDB06.SYSALTER
INCLUDE TABLESPACE DSNDB06.SYSTSASC
INCLUDE TABLESPACE DSNDB06.SYSEBCDC
INCLUDE TABLESPACE DSNDB06.SYSTSUNI
INCLUDE TABLESPACE DSNDB06.SYSXML
INCLUDE TABLESPACE DSNDB06.SYSTSXTM
INCLUDE TABLESPACE DSNDB06.SYSTSXTS
INCLUDE TABLESPACE DSNDB06.SYSTARG
INCLUDE TABLESPACE DSNDB06.SYSROLES
INCLUDE TABLESPACE DSNDB06.SYSCONTX
INCLUDE TABLESPACE DSNDB06.SYSRTSTS
INCLUDE TABLESPACE DSNDB06.SYSTSADT
INCLUDE TABLESPACE DSNDB06.SYSTSCTL
INCLUDE TABLESPACE DSNDB06.SYSTSCTR
INCLUDE TABLESPACE DSNDB06.SYSTSCTD
INCLUDE TABLESPACE DSNDB06.SYSTSPEN
INCLUDE TABLESPACE DSNDB06.SYSTSPDT
INCLUDE TABLESPACE DSNDB06.SYSTSPDO
INCLUDE TABLESPACE DSNDB06.SYSTSTPF
INCLUDE TABLESPACE DSNDB06.SYSTSPTX
INCLUDE TABLESPACE DSNDB06.SYSTSATW
INCLUDE TABLESPACE DSNDB06.SYSTSPRH
INCLUDE TABLESPACE DSNDB06.SYSTSPHX
INCLUDE TABLESPACE DSNDB06.SYSTSATS
INCLUDE TABLESPACE DSNDB06.SYSTSATX
INCLUDE TABLESPACE DSNDB06.SYSTSQRA
INCLUDE TABLESPACE DSNDB06.SYSTSPKC
INCLUDE TABLESPACE DSNDB06.SYSTSQRY
INCLUDE TABLESPACE DSNDB06.SYSTSQRP
INCLUDE TABLESPACE DSNDB06.SYSTSQRO


COPY LIST ICPYDB01 COPYDDN ICPYTPLT SHRLEVEL CHANGE PARALLEL
COPY LIST ICPYDB06 COPYDDN ICPYTPLT SHRLEVEL CHANGE PARALLEL


-- LETS DO SOME CLEANUP

MODIFY RECOVERY LIST ICPYDB01 DELETE AGE(70)
MODIFY RECOVERY LIST ICPYDB06 DELETE AGE(70)


-- AND LAST BUT NOT LEAST, SYSLGRNX AND SYSCOPY

COPY TABLESPACE DSNDB01.SYSLGRNX COPYDDN ICPYTPLT SHRLEVEL CHANGE
COPY TABLESPACE DSNDB06.SYSCOPY COPYDDN ICPYTPLT SHRLEVEL CHANGE

/*


best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden


________________________________
Från: Michael Arlebrandt <[login to unmask email]>
Skickat: den 23 oktober 2017 15:41
Till: [login to unmask email]
Ämne: [DB2-L] - SV: Wild card in listdef templates for copy


Hi Avram,


Sorry to say that wildcarding is not supported for catalog and directory objects.


From v12 Utility manual:


Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.


best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



-----End Original Message-----

Raymond Bell

Wild card in listdef templates for copy
(in response to Michael Arlebrandt)
Not only can you not wildcard them, you have to make sure you copy them in the correct order. Or at least, the right order for them to be useful to Recover if you should ever need them. What you really want is some way to say, oh, I dunno, COPY ... DB2CATALOG for example, and let the Copy utility work out what/when it needs to copy them, taking care of DB2 version and mode for you.

Wonder where you can get such a utility...

Or just keep using the up-to-date DSNTIJIC job.

Cheers,


Raymond

Raymond Bell
DB2 Database Administrator | IT Operations | Technology | RBS

From: Michael Arlebrandt [mailto:[login to unmask email]
Sent: 23 October 2017 14:41
To: [login to unmask email]
Subject: [DB2-L] - SV: Wild card in listdef templates for copy


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************


Hi Avram,



Sorry to say that wildcarding is not supported for catalog and directory objects.



From v12 Utility manual:



Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.



best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (“RBS” or “us”) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you give your consent to the monitoring of your e-mail communications with us.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Philip Sevetson

Wild card in listdef templates for copy
(in response to Raymond Bell)
**please note my email address change**
Not quite subtle enough. [AD] on this next time, please, Agent 86. :-)

Philip Sevetson
Computer Systems Manager
5 Manhattan West (33rd St at 10th Ave)
New York, NY 10001-2632
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

From: Bell, Raymond (IT Operations, Technology) [mailto:[login to unmask email]
Sent: Monday, October 23, 2017 9:56 AM
To: '[login to unmask email]'
Subject: [DB2-L] - RE: Wild card in listdef templates for copy

Not only can you not wildcard them, you have to make sure you copy them in the correct order. Or at least, the right order for them to be useful to Recover if you should ever need them. What you really want is some way to say, oh, I dunno, COPY … DB2CATALOG for example, and let the Copy utility work out what/when it needs to copy them, taking care of DB2 version and mode for you.

Wonder where you can get such a utility…

Or just keep using the up-to-date DSNTIJIC job.

Cheers,


Raymond

Raymond Bell
DB2 Database Administrator | IT Operations | Technology | RBS

From: Michael Arlebrandt [mailto:[login to unmask email]
Sent: 23 October 2017 14:41
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - SV: Wild card in listdef templates for copy


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************

Hi Avram,



Sorry to say that wildcarding is not supported for catalog and directory objects.



From v12 Utility manual:



Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.



best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
Attachments

  • image001.png (3.3k)

Michael Arlebrandt

SV: Wild card in listdef templates for copy
(in response to Philip Sevetson)
Agree Raymond,


and I'll vote for that RFE if you raise one ��


/Michael

________________________________
Från: Sevetson, Phil <[login to unmask email]>
Skickat: den 23 oktober 2017 15:58:04
Till: '[login to unmask email]'
Ämne: [DB2-L] - RE: Wild card in listdef templates for copy

**please note my email address change**
Not quite subtle enough. [AD] on this next time, please, Agent 86. :-)

Philip Sevetson
Computer Systems Manager
5 Manhattan West (33rd St at 10th Ave)
New York, NY 10001-2632
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

From: Bell, Raymond (IT Operations, Technology) [mailto:[login to unmask email]
Sent: Monday, October 23, 2017 9:56 AM
To: '[login to unmask email]'
Subject: [DB2-L] - RE: Wild card in listdef templates for copy

Not only can you not wildcard them, you have to make sure you copy them in the correct order. Or at least, the right order for them to be useful to Recover if you should ever need them. What you really want is some way to say, oh, I dunno, COPY … DB2CATALOG for example, and let the Copy utility work out what/when it needs to copy them, taking care of DB2 version and mode for you.

Wonder where you can get such a utility…

Or just keep using the up-to-date DSNTIJIC job.

Cheers,


Raymond

Raymond Bell
DB2 Database Administrator | IT Operations | Technology | RBS

From: Michael Arlebrandt [mailto:[login to unmask email]
Sent: 23 October 2017 14:41
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - SV: Wild card in listdef templates for copy


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************

Hi Avram,



Sorry to say that wildcarding is not supported for catalog and directory objects.



From v12 Utility manual:



Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.



best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



-----End Original Message-----

Raymond Bell

Wild card in listdef templates for copy
(in response to Michael Arlebrandt)
Duly rumbled. :o)

You can take the boy out of the company, etc.

I was always a big fan of the Cone of Silence. Probably working as designed too.

RFE, Michael? I think what you really need is a PO. ;o)


Raymond Bell
DB2 Database Administrator | IT Operations | Technology | RBS

From: Michael Arlebrandt [mailto:[login to unmask email]
Sent: 23 October 2017 15:05
To: [login to unmask email]
Subject: [DB2-L] - SV: Wild card in listdef templates for copy


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************


Agree Raymond,



and I'll vote for that RFE if you raise one ��



/Michael

________________________________
Från: Sevetson, Phil <[login to unmask email]<mailto:[login to unmask email]>>
Skickat: den 23 oktober 2017 15:58:04
Till: '[login to unmask email]'
Ämne: [DB2-L] - RE: Wild card in listdef templates for copy

**please note my email address change**
Not quite subtle enough. [AD] on this next time, please, Agent 86. :-)

Philip Sevetson
Computer Systems Manager
5 Manhattan West (33rd St at 10th Ave)
New York, NY 10001-2632
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

From: Bell, Raymond (IT Operations, Technology) [mailto:[login to unmask email]
Sent: Monday, October 23, 2017 9:56 AM
To: '[login to unmask email]'
Subject: [DB2-L] - RE: Wild card in listdef templates for copy

Not only can you not wildcard them, you have to make sure you copy them in the correct order. Or at least, the right order for them to be useful to Recover if you should ever need them. What you really want is some way to say, oh, I dunno, COPY … DB2CATALOG for example, and let the Copy utility work out what/when it needs to copy them, taking care of DB2 version and mode for you.

Wonder where you can get such a utility…

Or just keep using the up-to-date DSNTIJIC job.

Cheers,


Raymond

Raymond Bell
DB2 Database Administrator | IT Operations | Technology | RBS

From: Michael Arlebrandt [mailto:[login to unmask email]
Sent: 23 October 2017 14:41
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - SV: Wild card in listdef templates for copy


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************

Hi Avram,



Sorry to say that wildcarding is not supported for catalog and directory objects.



From v12 Utility manual:



Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.



best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (“RBS” or “us”) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you give your consent to the monitoring of your e-mail communications with us.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Kirk Hampton

Wild card in listdef templates for copy
(in response to Raymond Bell)
Other than the SYSUITLX first, SYSLGRNG and SYSCOP last,
Is there indeed a required “correct” order for all the others in the middle ?
Sorry, I have not read up on this in a good while.

At one of my clients a while back, they stopped using a non-IBM vendor’s utility to back up their catalog/directory and went back to the IBM utility.
I am unsure of the actual problem encountered, I just know that it happened.
I am sure that it was not on the current release of either DB2 or the vendor products.

J. Kirk Hampton
DB2 z/OS Sysprog
HCL America
Frisco, Texas
817-228-6083


From: Bell, Raymond (IT Operations, Technology) [mailto:[login to unmask email]
Sent: Monday, October 23, 2017 8:56 AM
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - RE: Wild card in listdef templates for copy

Not only can you not wildcard them, you have to make sure you copy them in the correct order. Or at least, the right order for them to be useful to Recover if you should ever need them. What you really want is some way to say, oh, I dunno, COPY … DB2CATALOG for example, and let the Copy utility work out what/when it needs to copy them, taking care of DB2 version and mode for you.

Wonder where you can get such a utility…

Or just keep using the up-to-date DSNTIJIC job.

Cheers,


Raymond

Raymond Bell
DB2 Database Administrator | IT Operations | Technology | RBS

From: Michael Arlebrandt [mailto:[login to unmask email]
Sent: 23 October 2017 14:41
To: [login to unmask email]
Subject: [DB2-L] - SV: Wild card in listdef templates for copy


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************

Hi Avram,



Sorry to say that wildcarding is not supported for catalog and directory objects.



From v12 Utility manual:



Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.



best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



-----End Original Message-----

Larry Jardine

Wild card in listdef templates for copy
(in response to Avram Friedman)
Of course what everyone has said regarding the need for specifying the full names of catalog and directory object applies.

You got the syntax error because of the superfluous “TABLESPACE”:

INCLUDE TABLESPACES TABLESPACE dbname.tswildcard

Larry Jardine
Senior Database Administrator

From: Avram Friedman [mailto:[login to unmask email]
Sent: Monday, October 23, 2017 9:33 AM
To: [login to unmask email]
Subject: [DB2-L] - Wild card in listdef templates for copy


Customer is DB2 v10 CM8
I am trying to bulld an IC job that will need few modifications for V10 NFM and beyond.

This is my Guess
//SYSIN DD *
OPTIONS EVENT ( ITEMERROR, SKIP )
LISTDEF LIST1
INCLUDE TABLESPACES TABLESPACE DSNDB01.*
INCLUDE TABLESPACES TABLESPACE DSNDB06.*
EXCLUDE TABLESPACES TABLESPACE DSNDB06.SYSCOPY
TEMPLATE ICOPY
DSN(SY.DSNT.&DB..&TS..D&DT..T&TI.)
DISP (NEW,CATLG,DELETE)
UNIT VTAPE
STACK YES
BUFNO 40
RETPD 31
COPY LIST LIST1 SHRLEVEL CHANGE
COPYDDN(ICOPY)

This is what I get
DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = IMAGCOPY
DSNUGTIS - PROCESSING SYSIN AS EBCDIC
DSNUGUTC - OPTIONS EVENT(ITEMERROR, SKIP)
DSNUZODR - OPTIONS STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - LISTDEF LIST1 INCLUDE TABLESPACES TABLESPACE DSNDB01.* INCLUDE TABL
TABLESPACES TABLESPACE DSNDB06.SYSCOPY
DSNUILDR - LISTDEF STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - TEMPLATE ICOPY DSN(SY.DSNT.&DB..&TS..D&DT..T&TI.) DISP(NEW, CATLG,
0 RETPD 31
DSNUJTDR - TEMPLATE STATEMENT PROCESSED SUCCESSFULLY
DSNUGUTC - COPY LIST LIST1 SHRLEVEL CHANGE COPYDDN(ICOPY)
DSNUILSA - INVALID KEYWORD SPECIFIED ON CLAUSE: INCLUDE TABLESPACE DSNDB01.%
DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8

All the IC samples I have seen in my research have each tablespace name completely spelled out.

Is this a requirement or can I get something like my hoped for method to work?



Avram Friedman
DB2-L hall of fame contributer
DB2-L acting administrator

[login to unmask email]<mailto:[login to unmask email]>

-----End Original Message-----

This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna

Peter Vanroose

Re: Wild card in listdef templates for copy
(in response to Kirk Hampton)

What I seem to remember having read somewhere in the manuals (just out of the top of my head):
first recover SYSCOPY, then the rest. (Of course, after the directory.)
So it's certainly clearly documented somewhere!  (Admin Guide I guess?)

In Reply to Kirk Hampton:

Other than the SYSUITLX first, SYSLGRNG and SYSCOP last,
Is there indeed a required “correct” order for all the others in the middle ?

--      Peter Vanroose
        ABIS Training & Consulting,
        Leuven, Belgium.
        http://www.abis.be/

Edited By:
Peter Vanroose[Organization Members] @ Oct 24, 2017 - 09:56 AM (Europe/Brussels)

Peter Vanroose

Re: Wild card in listdef templates for copy
(in response to Peter Vanroose)

Quoting from page 466 of the Admin Guide (Db2 11 for z/OS, document version of Oct 12, 2017), Chapter 12 "Backing up and recovering your data":

To prepare a point of consistency:
1. Display and resolve any indoubt units of recovery.
2. Use the COPY utility to make image copies of all data, including user data, Db2 catalog and directory table spaces, and optionally indexes. Copy SYSLGRNX and SYSCOPY last.
Installation job DSNTIJIC creates image copies of the Db2 catalog and directory table spaces. If you decide to copy your directory and catalog indexes, modify job DSNTIJIC to include those indexes.

And from page 625 (and this seems new in version 11 as compared to version 10 and before):

Image copies of DSNDB01.SYSUTILX, DSNDB01.DBD01, DSNDB06.SYSTSCPY, and DSNDB01.SYSDBDXA are registered in the DBET log record rather than in SYSIBM.SYSCOPY. During recovery, they are recovered from the log, and then image copies of other table spaces are located from the recovered SYSIBM.SYSCOPY.
(Note: DSNDB06.SYSTSCPY is the tablespace of SYSIBM.SYSCOPY)

Details are actually in the Utility Guide (version of Oct. 13, 2017), Chapter 27 "RECOVER";
on pages 494-496 it reads:

Requirement: You must recover the catalog and directory objects in the order that is specified in this task. If you are recovering any subset of the objects in the list, start with the object that is listed first and continue in the order of the list. For example, if you need to recover SYSLGRNX, SYSUTILX, and SYSUSER, recover SYSUTILX first, then SYSLGRNX, and then SYSUSER.

Procedure: to recover catalog and directory objects:
 1. Recover DSNDB01.SYSUTILX.
 2. Run REBUILD INDEX(ALL) on DSNDB01.SYSUTILX.
 3. Recover DSNDB01.DBD01.
 4. Run REBUILD INDEX(ALL) on DSNDB01.DBD01.
 5. Recover DSNDB01.SYSDBDXA.
 6. Run REBUILD INDEX(ALL) on DSNDB01.SYSDBDXA.
 7. Recover DSNDB06.SYSTSCPY.
 8. Run REBUILD INDEX(ALL) on DSNDB06.SYSTSCPY.
 9. Recover DSNDB01.SYSLGRNX.
10. Run REBUILD INDEX(ALL) on DSNDB01.SYSLGRNX.
11. Recover DSNDB06.SYSTSSTG and DSNDB06.SYSTSVOL.
12. Run REBUILD INDEX(ALL) on DSNDB06.SYSTSSTG and DSNDB06.SYSTSVOL.
13. Rebuild any user-defined indexes that are STOGROUP-managed on SYSIBM.SYSCOPY.
14. Recover all of the remaining catalog and directory table spaces in a single RECOVER utility statement with the PARALLEL option.

And in Chapter 15 "COPY" it reads on page 171 (and that's the only reference to image copying the catalog):

Use the DSNTIJIC installation job to create backup copies of catalog and directory objects.

--      Peter Vanroose
        ABIS Training & Consulting,
        Leuven, Belgium.
        http://www.abis.be/

David Baldon

Wild card in listdef templates for copy
(in response to Peter Vanroose)
Registration of the “special spaces” in the DB2 log is not new with V11 or were you referring to something else being new?

...David

From: Peter Vanroose [mailto:[login to unmask email]
Sent: Tuesday, October 24, 2017 3:32 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: Wild card in listdef templates for copy


Quoting from page 466 of the Admin Guide (Db2 11 for z/OS, document version of Oct 12, 2017), Chapter 12 "Backing up and recovering your data":

To prepare a point of consistency:
1. Display and resolve any indoubt units of recovery.
2. Use the COPY utility to make image copies of all data, including user data, Db2 catalog and directory table spaces, and optionally indexes. Copy SYSLGRNX and SYSCOPY last.
Installation job DSNTIJIC creates image copies of the Db2 catalog and directory table spaces. If you decide to copy your directory and catalog indexes, modify job DSNTIJIC to include those indexes.

And from page 625 (and this seems new in version 11 as compared to version 10 and before):

Image copies of DSNDB01.SYSUTILX, DSNDB01.DBD01, DSNDB06.SYSTSCPY, and DSNDB01.SYSDBDXA are registered in the DBET log record rather than in SYSIBM.SYSCOPY. During recovery, they are recovered from the log, and then image copies of other table spaces are located from the recovered SYSIBM.SYSCOPY.
(Note: DSNDB06.SYSTSCPY is the tablespace of SYSIBM.SYSCOPY)

Details are actually in the Utility Guide (version of Oct. 13, 2017), Chapter 27 "RECOVER";
on pages 494-496 it reads:

Requirement: You must recover the catalog and directory objects in the order that is specified in this task. If you are recovering any subset of the objects in the list, start with the object that is listed first and continue in the order of the list. For example, if you need to recover SYSLGRNX, SYSUTILX, and SYSUSER, recover SYSUTILX first, then SYSLGRNX, and then SYSUSER.

Procedure: to recover catalog and directory objects:
1. Recover DSNDB01.SYSUTILX.
2. Run REBUILD INDEX(ALL) on DSNDB01.SYSUTILX.
3. Recover DSNDB01.DBD01.
4. Run REBUILD INDEX(ALL) on DSNDB01.DBD01.
5. Recover DSNDB01.SYSDBDXA.
6. Run REBUILD INDEX(ALL) on DSNDB01.SYSDBDXA.
7. Recover DSNDB06.SYSTSCPY.
8. Run REBUILD INDEX(ALL) on DSNDB06.SYSTSCPY.
9. Recover DSNDB01.SYSLGRNX.
10. Run REBUILD INDEX(ALL) on DSNDB01.SYSLGRNX.
11. Recover DSNDB06.SYSTSSTG and DSNDB06.SYSTSVOL.
12. Run REBUILD INDEX(ALL) on DSNDB06.SYSTSSTG and DSNDB06.SYSTSVOL.
13. Rebuild any user-defined indexes that are STOGROUP-managed on SYSIBM.SYSCOPY.
14. Recover all of the remaining catalog and directory table spaces in a single RECOVER utility statement with the PARALLEL option.

And in Chapter 15 "COPY" it reads on page 171 (and that's the only reference to image copying the catalog):

Use the DSNTIJIC installation job to create backup copies of catalog and directory objects.

-- Peter Vanroose
ABIS Training & Consulting,
Leuven, Belgium.
http://www.abis.be/ https://urldefense.proofpoint.com/v2/url?u=http-3A__www.abis.be_html_enDB2Calendar.html&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=KigCN-TlaQoAQDZrna0ZVLUX9H9vZpSibySEyujWvHQ&m=dfH7yg8Lp0J7I0J8kqiu0XSpEaWnpJUsalVAMqOn0ko&s=kVtSzU84FdjRHenfTYj-CV42Td7tEUdmhQDe2tIVIx8&e=

-----End Original Message-----

Phil Grainger

Wild card in listdef templates for copy
(in response to Raymond Bell)
Seeing as IBM make the rules, you’d think that a listdef of dsndb01 and 6 WOULD put things in the “right” order…….
________________________________

Phil Grainger

Enablement Manager

[login to unmask email]

Direct



+44 (0)118 921 8000

Mobile



+44(0)7808 643 479


E2, Eskdale Road
Winnersh
Berkshire
RG41 5TS


[http://media.cms.bmc.com/images/corp_signature_bmclogo_2014.jpg] http://www.bmc.com

[cid:[login to unmask email]






From: Bell, Raymond (IT Operations, Technology) [mailto:[login to unmask email]
Sent: 23 October 2017 14:56
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - RE: Wild card in listdef templates for copy

Not only can you not wildcard them, you have to make sure you copy them in the correct order. Or at least, the right order for them to be useful to Recover if you should ever need them. What you really want is some way to say, oh, I dunno, COPY … DB2CATALOG for example, and let the Copy utility work out what/when it needs to copy them, taking care of DB2 version and mode for you.

Wonder where you can get such a utility…

Or just keep using the up-to-date DSNTIJIC job.

Cheers,


Raymond

Raymond Bell
DB2 Database Administrator | IT Operations | Technology | RBS

From: Michael Arlebrandt [mailto:[login to unmask email]
Sent: 23 October 2017 14:41
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - SV: Wild card in listdef templates for copy


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************

Hi Avram,



Sorry to say that wildcarding is not supported for catalog and directory objects.



From v12 Utility manual:



Pattern-matching is not supported for catalog and directory objects. In a LISTDEF statement, you must include catalog and directory objects by their fully qualified names.



best regards

Michael Arlebrandt

HCL

Gothenburg, Sweden



-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.
Attachments

  • image001.jpg (8k)
  • image002.png (5.9k)

J&#248;rn Thyssen

[AD] RE: Wild card in listdef templates for copy
(in response to Raymond Bell)

Speaking of tools: IBM Db2 Automation tool can generate a job to copy catalog and directory.

One of the samples provided is exactly that: adapt the IC settings to your site standards and generate job.
 

Best regards,

Jørn Thyssen

Rocket Software
77 Fourth Avenue • Waltham, MA • 02451 • USA
E: [login to unmask email] • W: www.rocketsoftware.com 

Views are personal. 

James Campbell

Wild card in listdef templates for copy
(in response to Phil Grainger)
Remembering that:

"Specify the DSNDB01.SYSUTILX, DSNDB06.SYSTSCPY, or
DSNDB01.SYSLGRNX table space by itself in a single COPY statement."

"To run on DSNDB01.SYSUTILX, COPY must be the only utility in the job step."

"Restriction: Utilities do not support SYSUTILX-related objects inside a LISTDEF
specification."

(Utility Reference)

So more than a simple change to what a listdef generates.

James Campbell


On 24 Oct 2017 at 14:30, Grainger, Phil wrote:

>
> Seeing as IBM make the rules, you´d think that a listdef of dsndb01 and 6 WOULD put
> things in the "right"order.......