Bring A Friend! 2019 IDUG Db2 Tech Conference in Charlotte, North Carolina

Nemi Agrawal

Bring A Friend! 2019 IDUG Db2 Tech Conference in Charlotte, North Carolina

I am working on DB2 for more than 15 years but never went to IDUG; This year, I would like to visit and looking for a sponsor for Bring A Friend! I am from Washington DC area and work for a Govt Contract. Appreciate for guidance/help if anyone going to Charlotte.

Nemi Agrawal

IT Consultant and CEO - Artha INc

 

Anton Britz

Deleting rows from SYSIBM.SYSCOPY ?
(in response to Nemi Agrawal)

Question : I was asked yesterday to delete rows from SYSIBM.SYSCOPY

Why ?

a MERGECOPY was done with 4 incremental backups but the output FULL IMAGE COPY was lost and then I was asked to delete the "Full Image" copy record/row in SYSIBM.SYSCOPY but we could not delete this record/row
Any suggestions
A'ton

Srinivas Adupa

Deleting rows from SYSIBM.SYSCOPY ?
(in response to Anton Britz)
Are you using MODIFY RECOVERY ?

On Sat, 2 Mar 2019, 10:40 pm Anton Britz, <[login to unmask email]> wrote:

> Question : I was asked yesterday to delete rows from SYSIBM.SYSCOPY
>
> Why ?
>
> a MERGECOPY was done with 4 incremental backups but the output FULL IMAGE
> COPY was lost and then I was asked to delete the "Full Image" copy
> record/row in SYSIBM.SYSCOPY but we could not delete this record/row
>
> Any suggestions
>
> A'ton
>
> ------------------------------
>
>
> -----End Original Message-----
>

Roy Boxwell

Deleting rows from SYSIBM.SYSCOPY ?
(in response to Anton Britz)
If you really need to you can make syscopy updatable and just delete the row... naturally you should never do this... modify recovery is the ibm recommended way and then a FIC as soon as you can afterwards of course!

Roy Boxwell
SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-
Heinrichstrasse 83-85
40239 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]
http://www.seg.de
Link zur Datenschutzerklärung

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

> On 2 Mar 2019, at 18:10, Anton Britz <[login to unmask email]> wrote:
>
> Question : I was asked yesterday to delete rows from SYSIBM.SYSCOPY
>
> Why ?
>
> a MERGECOPY was done with 4 incremental backups but the output FULL IMAGE COPY was lost and then I was asked to delete the "Full Image" copy record/row in SYSIBM.SYSCOPY but we could not delete this record/row
>
> Any suggestions
>
> A'ton
>
>
> Site Links: View post online View mailing list online Start new thread via email Unsubscribe from this mailing list Manage your subscription
>
> This email has been sent to: [login to unmask email]
> ESAi has well-regarded tools for Fast Cloning, Buffer Pool Tuning, Log Analysis, TDM & more.
> BCV4, BCV5, BPA4DB2, ULT4DB2... modern power tools to get the job done faster & easier than ever.
> http://www.ESAIGroup.com/idug
>
>
> Use of this email content is governed by the terms of service at:
> http://www.idug.org/p/cm/ld/fid=2
>
Attachments

  • smime.p7s (3.9k)

Phil Grainger

Deleting rows from SYSIBM.SYSCOPY ?
(in response to Roy Boxwell)
Of course, there is no real need to delete the row anyway. If you need to do a recovery, DB2 can skip missing copies

Also, hopefully only Roy and I toss aro7nd phrases like “... you can make SYSCOPY updatable”. Thus comes under the ‘do not try this at home category!

Phil G
________________________________
From: Boxwell, Roy <[login to unmask email]>
Sent: 03 March 2019 11:35:52
To: [login to unmask email]
Subject: [EXTERNAL] [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ?

If you really need to you can make syscopy updatable and just delete the row... naturally you should never do this... modify recovery is the ibm recommended way and then a FIC as soon as you can afterwards of course!

Roy Boxwell
SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-
Heinrichstrasse 83-85
40239 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de https://urldefense.proofpoint.com/v2/url?u=http-3A__www.seg.de&d=DwMGaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=0Pqp3zkoObGS269ePar1H0G2mpj-FuK-0TNVdKxzHfg&s=A-scdP4jTTCIK0Hpt3stup7D5n6l7m3YZPHZD3YAmGg&e=
Link zur Datenschutzerklärung https://urldefense.proofpoint.com/v2/url?u=https-3A__www.seg.de_corporate_rechtliche-2Dhinweise_datenschutz_&d=DwMGaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=0Pqp3zkoObGS269ePar1H0G2mpj-FuK-0TNVdKxzHfg&s=EB9_J0Uj92NlFHuAi6qemVzXDL2IPxFYKMM7bCWzW6k&e=

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

On 2 Mar 2019, at 18:10, Anton Britz <[login to unmask email]<mailto:[login to unmask email]>> wrote:


Question : I was asked yesterday to delete rows from SYSIBM.SYSCOPY

Why ?

a MERGECOPY was done with 4 incremental backups but the output FULL IMAGE COPY was lost and then I was asked to delete the "Full Image" copy record/row in SYSIBM.SYSCOPY but we could not delete this record/row

Any suggestions

A'ton

________________________________

-----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.

Raymond Bell

Deleting rows from SYSIBM.SYSCOPY ?
(in response to Phil Grainger)
If you really want to remove a specific row from Syscopy I'm aware of at least one major vendor's Copy utility that will do that for you. You can be as surgical as you like. Perfect for when Db2 thinks the IC dataset exists but it actually doesn't.

Cheers,


Raymond

From: Grainger, Phil [mailto:[login to unmask email]
Sent: 03 March 2019 13:58
To: [login to unmask email]
Subject: [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ?


*********************************************
" 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"
*********************************************

Of course, there is no real need to delete the row anyway. If you need to do a recovery, DB2 can skip missing copies

Also, hopefully only Roy and I toss aro7nd phrases like "... you can make SYSCOPY updatable". Thus comes under the 'do not try this at home category!

Phil G
________________________________
From: Boxwell, Roy <[login to unmask email]>
Sent: 03 March 2019 11:35:52
To: [login to unmask email]
Subject: [EXTERNAL] [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ?

If you really need to you can make syscopy updatable and just delete the row... naturally you should never do this... modify recovery is the ibm recommended way and then a FIC as soon as you can afterwards of course!
Roy Boxwell
SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-
Heinrichstrasse 83-85
40239 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de https://urldefense.proofpoint.com/v2/url?u=http-3A__www.seg.de&d=DwMGaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=0Pqp3zkoObGS269ePar1H0G2mpj-FuK-0TNVdKxzHfg&s=A-scdP4jTTCIK0Hpt3stup7D5n6l7m3YZPHZD3YAmGg&e=
Link zur Datenschutzerklärung https://urldefense.proofpoint.com/v2/url?u=https-3A__www.seg.de_corporate_rechtliche-2Dhinweise_datenschutz_&d=DwMGaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=0Pqp3zkoObGS269ePar1H0G2mpj-FuK-0TNVdKxzHfg&s=EB9_J0Uj92NlFHuAi6qemVzXDL2IPxFYKMM7bCWzW6k&e=

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

On 2 Mar 2019, at 18:10, Anton Britz <[login to unmask email]<mailto:[login to unmask email]>> wrote:

Question : I was asked yesterday to delete rows from SYSIBM.SYSCOPY

Why ?

a MERGECOPY was done with 4 incremental backups but the output FULL IMAGE COPY was lost and then I was asked to delete the "Full Image" copy record/row in SYSIBM.SYSCOPY but we could not delete this record/row

Any suggestions

A'ton
-----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.
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. 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 understand that the content of your message may be monitored.

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

Anton Britz

Deleting rows from SYSIBM.SYSCOPY ?
(in response to Raymond Bell)

Feedback:

One of the guys that removed the snow in our car park this morning , just told me about the bit in DSNZPARMS that I have to flip.
Thanks Raymond/Phil/Roy for the feedback but the pointer to DSNZPARMS was all I needed.
https://www.youtube.com/watch?v=pL0bxewHbjo

Anton
On 3/4/2019 3:02 AM, Bell, Raymond (Hosting Services, Technology) wrote:
If you really want to remove a specific row from Syscopy I’m aware of at least one major vendor’s Copy utility that will do that for you.  You can be as surgical as you like.  Perfect for when Db2 thinks the IC dataset exists but it actually doesn’t. Cheers, Raymond From: Grainger, Phil [mailto:[login to unmask email]
Sent: 03 March 2019 13:58
To: [login to unmask email]
Subject: [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ?
*********************************************
" 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"
*********************************************

Of course, there is no real need to delete the row anyway. If you need to do a recovery, DB2 can skip missing copies

Also, hopefully only Roy and I toss aro7nd phrases like “... you can make SYSCOPY updatable”. Thus comes under the ‘do not try this at home category!

Phil G From: Boxwell, Roy <[login to unmask email]>
Sent: 03 March 2019 11:35:52
To: [login to unmask email]
Subject: [EXTERNAL] [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ? If you really need to you can make syscopy updatable and just delete the row... naturally you should never do this... modify recovery is the ibm recommended way and then a FIC as soon as you can afterwards of course!Roy Boxwell SOFTWARE ENGINEERING GmbH and SEGUS Inc.-Product Development-Heinrichstrasse 83-8540239 Düsseldorf/GermanyTel. +49 (0)211 96149-675Fax +49 (0)211 96149-32Email: [login to unmask email]http://www.seg.deLink zur Datenschutzerklärung Software Engineering GmbHAmtsgericht Düsseldorf, HRB 37894Geschäftsführung: Gerhard Schubert, Ulf Heinrich 
On 2 Mar 2019, at 18:10, Anton Britz <[login to unmask email]> wrote:
Question : I was asked yesterday to delete rows from SYSIBM.SYSCOPY
Why ?
a MERGECOPY was done with 4 incremental backups but the output FULL IMAGE COPY was lost and then I was asked to delete the "Full Image" copy record/row in SYSIBM.SYSCOPY but we could not delete this record/row
Any suggestions
A'ton-----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. -----End Original Message-----The Royal Bank of Scotland plc. Registered in Scotland No 83026. 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: 250 Bishopsgate, London EC2M 4AA.  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 understand that the content of your message may be monitored.   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
Site Links: View post online   View mailing list online   Start new thread via email   Unsubscribe from this mailing list   Manage your subscription  

This email has been sent to: [login to unmask email]
ESAi has well-regarded tools for Fast Cloning, Buffer Pool Tuning, Log Analysis, TDM & more.
BCV4, BCV5, BPA4DB2, ULT4DB2... modern power tools to get the job done faster & easier than ever.
http://www.ESAIGroup.com/idug


Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2

Bill Gallagher

Deleting rows from SYSIBM.SYSCOPY ?
(in response to Anton Britz)
Never underestimate the talents of a good plow guy!

Bill Gallagher | Senior Systems Engineer, DBA | Data Administration

From: Anton Britz <[login to unmask email]>
Sent: Monday, March 4, 2019 11:44 AM
To: [login to unmask email]
Subject: [External] [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ?


Feedback:

One of the guys that removed the snow in our car park this morning , just told me about the bit in DSNZPARMS that I have to flip.

Thanks Raymond/Phil/Roy for the feedback but the pointer to DSNZPARMS was all I needed.

https://www.youtube.com/watch?v=pL0bxewHbjo

Anton
On 3/4/2019 3:02 AM, Bell, Raymond (Hosting Services, Technology) wrote:
If you really want to remove a specific row from Syscopy I'm aware of at least one major vendor's Copy utility that will do that for you. You can be as surgical as you like. Perfect for when Db2 thinks the IC dataset exists but it actually doesn't.

Cheers,


Raymond

From: Grainger, Phil [mailto:[login to unmask email]
Sent: 03 March 2019 13:58
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ?


*********************************************
" 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"
*********************************************


Of course, there is no real need to delete the row anyway. If you need to do a recovery, DB2 can skip missing copies

Also, hopefully only Roy and I toss aro7nd phrases like "... you can make SYSCOPY updatable". Thus comes under the 'do not try this at home category!

Phil G
________________________________
From: Boxwell, Roy <[login to unmask email]><mailto:[login to unmask email]>
Sent: 03 March 2019 11:35:52
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [EXTERNAL] [DB2-L] - RE: Deleting rows from SYSIBM.SYSCOPY ?

If you really need to you can make syscopy updatable and just delete the row... naturally you should never do this... modify recovery is the ibm recommended way and then a FIC as soon as you can afterwards of course!
Roy Boxwell
SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-
Heinrichstrasse 83-85
40239 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de https://urldefense.proofpoint.com/v2/url?u=http-3A__www.seg.de&d=DwMGaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=0Pqp3zkoObGS269ePar1H0G2mpj-FuK-0TNVdKxzHfg&s=A-scdP4jTTCIK0Hpt3stup7D5n6l7m3YZPHZD3YAmGg&e=
Link zur Datenschutzerklärung https://urldefense.proofpoint.com/v2/url?u=https-3A__www.seg.de_corporate_rechtliche-2Dhinweise_datenschutz_&d=DwMGaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=0Pqp3zkoObGS269ePar1H0G2mpj-FuK-0TNVdKxzHfg&s=EB9_J0Uj92NlFHuAi6qemVzXDL2IPxFYKMM7bCWzW6k&e=

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

On 2 Mar 2019, at 18:10, Anton Britz <[login to unmask email]<mailto:[login to unmask email]>> wrote:

Question : I was asked yesterday to delete rows from SYSIBM.SYSCOPY

Why ?

a MERGECOPY was done with 4 incremental backups but the output FULL IMAGE COPY was lost and then I was asked to delete the "Full Image" copy record/row in SYSIBM.SYSCOPY but we could not delete this record/row

Any suggestions

A'ton
-----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.
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. 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: 250 Bishopsgate, London EC2M 4AA. 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 understand that the content of your message may be monitored.

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
-----End Original Message-----

-----End Original Message-----
________________________________
This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.

TRVDiscDefault::1201