You still need to have your DATA statement.
Craig
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mainframe Mainframe
Sent: Wednesday, December 23, 2015 11:09
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF Catalog
Hello
Of Mainframe Mainframe
Sent: Wednesday, December 23, 2015 11:09
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF Catalog
Hello ,
Hope you are doing good. we have system in sysplex and
for different versionz/OS system in sysplex we have different master
catalog.
Now i created
On Wed, Dec 23, 2015 at 11:09 AM, Mainframe Mainframe <
mainframe1...@gmail.com> wrote:
> Hello ,
> Hope you are doing good. we have system in sysplex and
> for different versionz/OS system in sysplex we have different master
> catalog.
> Now i created IODF from one z/OS
Hello ,
Hope you are doing good. we have system in sysplex and
for different versionz/OS system in sysplex we have different master
catalog.
Now i created IODF from one z/OS system and its catalog under this system
master catalog. But to access this same IODF from
t: Wednesday, December 23, 2015 9:09 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IODF Catalog
>
> Hello ,
> Hope you are doing good. we have system in sysplex and
> for different versionz/OS system in sysplex we have different master
> catalog.
> Now
I forgot to add IDCAMS output for this
IDCAMS SYSTEM SERVICES TIME:
23:11:16
/* IDCAMS COMMAND */
LISTCAT ENTRIES(SYS1.IODF11.WORK) -
ALL
DATA -- SYS1.IODF11.WORK
IN-CAT ---SYS1.MASTER.CATALOG
HISTORY
] On
Behalf Of venkat kulkarni
Sent: Sunday, September 28, 2014 10:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF catalog issue
Hello Group,
By mistake somebody from our team run below Job, which
has
cataloged SYS1.IODF11.WORK file into master catalog as user catalog
-MAIN@LISTSERV.UA.EDU]
On Behalf Of venkat kulkarni
Sent: Sunday, September 28, 2014 10:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF catalog issue
Hello Group,
By mistake somebody from our team run below Job,
which has cataloged SYS1.IODF11.WORK file
, September 29, 2014 7:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IODF catalog issue
You might want to go to IBM for assistance.
They may be able to help you fix your issue.
VSAM can be difficult in fixing issues depending on how hard you worked
to create
an issue.
Lizette
Hello Group,
By mistake somebody from our team run below Job, which
has cataloged SYS1.IODF11.WORK file into master catalog as user catalog.
//IMPCONET JOB 'VENKAT',CLASS=A,MSGCLASS=A,NOTIFY=SYSUID
//IMPORT EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
IMPORT -
Sorry for late reply, as I was out of office. Thanks for all help. Problem
has been resolved by following below parm.
DEFINE CLUSTER(NAME(SYS1.iodf.CLUSTER) -
VOLUME(volser) -
RECATALOG ) -
CAT(second.catalog)
Thanks once again.
On Mon, Sep 22, 2014 at
I have IODF defined in one system and want to work on the IODF using HCD
from another system but its not cataloged into new system. Volumes are
shared in this case.
Is there any way to catalog the current IODF to new system as well .
Yes, but _ONLY_ if the high level qualitier is SYS1. It is is
_anything_ else, then NO. There is special logic somewhere in DFP
which allows any SYS1 data set to be catalogued in any catalog, even
if it is not the catalog in the VVDS for the data set.
DEFINE CLUSTER(NAME(SYS1.iodf.CLUSTER) -
-MAIN@LISTSERV.UA.EDU] On Behalf
Of venkat kulkarni
Sent: Monday, September 22, 2014 3:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF catalog issue
I have IODF defined in one system and want to work on the IODF using HCD from
another system but its not cataloged into new system. Volumes
to it from both systems with no issues.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of venkat kulkarni
Sent: Monday, September 22, 2014 3:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF catalog issue
I have IODF defined in one
-MAIN@LISTSERV.UA.EDU] On
Behalf Of venkat kulkarni
Sent: Monday, September 22, 2014 12:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF catalog issue
I have IODF defined in one system and want to work on the IODF using HCD
from
another system but its not cataloged into new system. Volumes
...@listserv.ua.edu] On Behalf Of venkat kulkarni
Sent: Monday, September 22, 2014 3:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF catalog issue
I have IODF defined in one system and want to work on the IODF
using HCD from another system but its not cataloged into new
system. Volumes are shared
On Mon, 22 Sep 2014 06:42:27 -0500, John McKown wrote:
Again, and I cannot stress enough, this works IF AND ONLY IF the high
level qualifier is SYS1. No exceptions.
Wanna bet ?.
Shane ...
--
For IBM-MAIN subscribe / signoff /
and get to it from both systems with no issues.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of venkat kulkarni
Sent: Monday, September 22, 2014 3:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IODF catalog issue
I have IODF defined
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of John McKown
Sent: Monday, September 22, 2014 4:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IODF catalog issue
Yes, but _ONLY_ if the high level qualitier is SYS1. It is is _anything_
else, then
NO. There is special
@LISTSERV.UA.EDU
Subject: Re: IODF catalog issue
On Mon, Sep 22, 2014 at 8:42 AM, Shane Ginnane ibm-m...@tpg.com.au
wrote:
On Mon, 22 Sep 2014 06:42:27 -0500, John McKown wrote:
Again, and I cannot stress enough, this works IF AND ONLY IF the high
level qualifier is SYS1. No exceptions
21 matches
Mail list logo
