[zos] J0002, J0003, J0004, J0005

Ivan L

[zos] J0002, J0003, J0004, J0005
Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan



Banco de España - Aviso legal

Este mensaje, su contenido y cualquier fichero transmitido
con él está dirigido únicamente a su destinatario y es
confidencial. Por ello, se informa a quien lo reciba por error o
tenga conocimiento del mismo sin ser su destinatario, que la
información contenida en él es reservada y su uso no
autorizado, por lo que en tal caso le rogamos nos lo comunique
por la misma vía o por teléfono (+ 34 91 338 66 66), así como
que se abstenga de reproducir el mensaje mediante cualquier
medio o remitirlo o entregarlo a otra persona, procediendo a su
borrado de manera inmediata.

El Banco de España se reserva las acciones legales que le
correspondan contra todo tercero que acceda de forma
ilegítima al contenido de cualquier mensaje externo procedente
del mismo.

Para informacion y consultas visite nuestra web
http://www.bde.es


Banco de España - Disclaimer
This message, its content and any file attached thereto is for
the intended recipient only and is confidential. If you have
received this e-mail in error or had access to it, you should
note that the information in it is private and any use thereof
is unauthorised. In such an event please notify us by e-mail or
by telephone (+ 34 91 338 66 66). Any reproduction of this
e-mail by whatsoever means and any transmission or dissemination
thereof to other persons is prohibited. It should be deleted
immediately from your system.

The Banco de España reserves the right to take legal action
against any persons unlawfully gaining access to the content of
any external message it has emitted.

For additional information, please visit our website
http://www.bde.es

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Wayne Driscoll

Re: [zos] J0002, J0003, J0004, J0005
(in response to Ivan L)
The Jnnnn datasets are created from an online reorg. When using online
reorg, the prefix for this qualifier alternates between "I" and "J", see
column IPREFIX in SYSINDEXPART/SYSTABLEPART to see which is currently
being used.

Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.




-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of [login to unmask email]
Sent: Wednesday, December 05, 2007 2:15 AM
To: [login to unmask email]
Subject: [DB2-L] [zos] J0002, J0003, J0004, J0005

Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mike Turner

Re: [zos] J0002, J0003, J0004, J0005
(in response to Wayne Driscoll)
Hi Wayne

That explains the J, but surely not the 0002, 0003, etc. The Reorg will
always use J0001, never J0002. V9 clone tables may create I0002 and J0002
datasets, but this is not supported in V8. My guess would be that these
datasets were created by a person and not by DB2.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722. Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB 338
4159 44.

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of Wayne Driscoll
Sent: Wednesday, 05 December 2007 14:26
To: [login to unmask email]
Subject: Re: [DB2-L] [zos] J0002, J0003, J0004, J0005



The Jnnnn datasets are created from an online reorg. When using online
reorg, the prefix for this qualifier alternates between "I" and "J", see
column IPREFIX in SYSINDEXPART/SYSTABLEPART to see which is currently
being used.

Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.




-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of [login to unmask email]
Sent: Wednesday, December 05, 2007 2:15 AM
To: [login to unmask email]
Subject: [DB2-L] [zos] J0002, J0003, J0004, J0005

Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th.
Details at http://www.idug.org

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins canbe reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mark Vickers

Re: [zos] J0002, J0003, J0004, J0005
(in response to Mike Turner)
I think the 0002, 0003 etc. are from the space limit being reached - e.g.
2G limit - when that is reached, DB2 will take another physical dataset.
The index or table space appears as normal, but under the covers there can
be more than one linear vsam dataset.
Mark.



Mike Turner <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/05/2007 10:27 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [zos] J0002, J0003, J0004, J0005






Hi Wayne

That explains the J, but surely not the 0002, 0003, etc. The Reorg will
always use J0001, never J0002. V9 clone tables may create I0002 and J0002
datasets, but this is not supported in V8. My guess would be that these
datasets were created by a person and not by DB2.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722.
Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB
338
4159 44.

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of Wayne Driscoll
Sent: Wednesday, 05 December 2007 14:26
To: [login to unmask email]
Subject: Re: [DB2-L] [zos] J0002, J0003, J0004, J0005



The Jnnnn datasets are created from an online reorg. When using online
reorg, the prefix for this qualifier alternates between "I" and "J", see
column IPREFIX in SYSINDEXPART/SYSTABLEPART to see which is currently
being used.

Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.




-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of [login to unmask email]
Sent: Wednesday, December 05, 2007 2:15 AM
To: [login to unmask email]
Subject: [DB2-L] [zos] J0002, J0003, J0004, J0005

Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th.
Details at http://www.idug.org

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select
"Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org.
The IDUG List Admins canbe reached at [login to unmask email]
Find
out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th.
Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm





This e-mail (and any attachments) may contain information that is
confidential and/or protected by law. Any review, use, distribution or
disclosure to anyone other than the
intended recipient(s) is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete all copies
of this message.



IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mike Turner

Re: [zos] J0002, J0003, J0004, J0005
(in response to Mark Vickers)
Hi Mark

But surely those new datasets would change the last qualifier and use A002,
A003, etc, not change the 5th qualifier I0001 or J0001.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722. Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB 338
4159 44.
-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]On
Behalf Of [login to unmask email]
Sent: Wednesday, 05 December 2007 16:41
To: [login to unmask email]
Subject: Re: [DB2-L] [zos] J0002, J0003, J0004, J0005



I think the 0002, 0003 etc. are from the space limit being reached - e.g.
2G limit - when that is reached, DB2 will take another physical dataset.
The index or table space appears as normal, but under the covers there can
be more than one linear vsam dataset.
Mark.


Mike Turner <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/05/2007 10:27 AM Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>

[login to unmask email]
cc
SubjectRe: [zos] J0002, J0003, J0004, J0005







Hi Wayne

That explains the J, but surely not the 0002, 0003, etc. The Reorg will
always use J0001, never J0002. V9 clone tables may create I0002 and J0002
datasets, but this is not supported in V8. My guess would be that these
datasets were created by a person and not by DB2.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722. Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB 338
4159 44.

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of Wayne Driscoll
Sent: Wednesday, 05 December 2007 14:26
To: [login to unmask email]
Subject: Re: [DB2-L] [zos] J0002, J0003, J0004, J0005



The Jnnnn datasets are created from an online reorg. When using online
reorg, the prefix for this qualifier alternates between "I" and "J", see
column IPREFIX in SYSINDEXPART/SYSTABLEPART to see which is currently
being used.

Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.




-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of [login to unmask email]
Sent: Wednesday, December 05, 2007 2:15 AM
To: [login to unmask email]
Subject: [DB2-L] [zos] J0002, J0003, J0004, J0005

Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th.
Details at http://www.idug.org

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins canbe reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th.
Details at http://www.idug.org

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm





This e-mail (and any attachments) may contain information that is
confidential and/or protected by law. Any review, use, distribution or
disclosure to anyone other than the
intended recipient(s) is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete all copies of
this message.


IMPORTANT NOTICE:
IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th. Details
at http://www.idug.org
----------------------------------------------------------------------------
----- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Phil Grainger

Re: [zos] J0002, J0003, J0004, J0005
(in response to Mike Turner)
but don't additional datasets increment the LAST node not the penultimate one (A002, A003, A004 etc etc)???

In DB2 9, the "I" node is the instance number (for cloning) and can have values of either I/J0001 OR I/J0002 and NOTHING else.

I suspect these are left over from some other, long forgotten non-DB2 event - especially as you say that J0001 is missing

HMIGRATE them and see if anything calls them back in the near future....

Phil Grainger
CA

________________________________

From: DB2 Data Base Discussion List on behalf of [login to unmask email]
Sent: Wed 05/12/2007 16:41
To: [login to unmask email]
Subject: Re: [DB2-L] [zos] J0002, J0003, J0004, J0005



I think the 0002, 0003 etc. are from the space limit being reached - e.g. 2G limit - when that is reached, DB2 will take another physical dataset.
The index or table space appears as normal, but under the covers there can be more than one linear vsam dataset.
Mark.



Mike Turner <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>

12/05/2007 10:27 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc
Subject
Re: [zos] J0002, J0003, J0004, J0005






Hi Wayne

That explains the J, but surely not the 0002, 0003, etc. The Reorg will
always use J0001, never J0002. V9 clone tables may create I0002 and J0002
datasets, but this is not supported in V8. My guess would be that these
datasets were created by a person and not by DB2.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722. Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB 338
4159 44.

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of Wayne Driscoll
Sent: Wednesday, 05 December 2007 14:26
To: [login to unmask email]
Subject: Re: [DB2-L] [zos] J0002, J0003, J0004, J0005



The Jnnnn datasets are created from an online reorg. When using online
reorg, the prefix for this qualifier alternates between "I" and "J", see
column IPREFIX in SYSINDEXPART/SYSTABLEPART to see which is currently
being used.

Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.




-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of [login to unmask email]
Sent: Wednesday, December 05, 2007 2:15 AM
To: [login to unmask email]
Subject: [DB2-L] [zos] J0002, J0003, J0004, J0005

Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th.
Details at http://www.idug.org

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins canbe reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm






This e-mail (and any attachments) may contain information that is confidential and/or protected by law. Any review, use, distribution or disclosure to anyone other than the
intended recipient(s) is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and delete all copies of this message.




IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

--------------------------------------------------------------------------------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm


IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mark Vickers

Re: [zos] J0002, J0003, J0004, J0005
(in response to Phil Grainger)
Mike,
I do know that a partitioned space uses A001, A002 etc. for the last
qualifier.

I am going to double check myself on the 5th qualifier.

Mark.



Mike Turner <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/05/2007 10:51 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [zos] J0002, J0003, J0004, J0005






Hi Mark

But surely those new datasets would change the last qualifier and use
A002,
A003, etc, not change the 5th qualifier I0001 or J0001.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722.
Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB
338
4159 44.
-----Original Message-----

Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan






This e-mail (and any attachments) may contain information that is
confidential and/or protected by law. Any review, use, distribution or
disclosure to anyone other than the
intended recipient(s) is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete all copies
of this message.



IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mark Vickers

Re: [zos] J0002, J0003, J0004, J0005
(in response to Mark Vickers)
Well, I tested it and I was wrong, both (partitioned and >limit) increment
the last qualifier.

So I guess Phil's suggestion of some old process hangover may be the
answer ?

Sorry for the cofusion.
Mark.




[login to unmask email]
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/05/2007 11:06 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [zos] J0002, J0003, J0004, J0005







Mike,
I do know that a partitioned space uses A001, A002 etc. for the last
qualifier.

I am going to double check myself on the 5th qualifier.

Mark.


Mike Turner <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/05/2007 10:51 AM

Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [zos] J0002, J0003, J0004, J0005








Hi Mark

But surely those new datasets would change the last qualifier and use
A002,
A003, etc, not change the 5th qualifier I0001 or J0001.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722.
Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB
338
4159 44.
-----Original Message-----

Hi, list:

While moving DB2 vsam's we've seen this:

BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0002.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0003.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0004.A001
BDTPR.DSNDBD.BDXYZ002.XYZR1TMM.J0005.A001

What are this files J0002, J0003, J0004...??

XYZR1TMN was an indexspace, and J0001 not exist because a DROP INDEX (i
supose). We are in v8nfn.

TIA

Regards

Ivan





This e-mail (and any attachments) may contain information that is
confidential and/or protected by law. Any review, use, distribution or
disclosure to anyone other than the
intended recipient(s) is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete all copies
of this message.

IMPORTANT NOTICE:
IDUG is pleased to announce a series of upgrades to the DB2-L discussion
listserv that are being implemented to improve reliability and the overall
user experience of DB2-L. These changes are coming on November 30th.
Details at http://www.idug.org
---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm




This e-mail (and any attachments) may contain information that is
confidential and/or protected by law. Any review, use, distribution or
disclosure to anyone other than the
intended recipient(s) is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete all copies
of this message.



IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm