|
View previous topic :: View next topic
|
| Author |
Message |
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
My system is running off the z/Os 2.4 ADCD, and I wanted to access a ZFS filesystem from the
D5PRD1 volume which was downloaded with the 2.5 ADCD.
The volume is mounted and accessible on the 2.,4 system.
However, the VSAM clusters are not cataloged.
This volume has a usercatalog named: 'USERCAT.Z25D.PRODS'
I tried doing the following IMPORT:
IDCAMS SYSTEM SERVICES
IMPORT CONNECT ALIAS -
OBJECTS((USERCAT.Z25D.PRODS VOLUMES(D5PRD1) -
DEVT(3390))) -
CAT(CATALOG.Z24D.MASTER)
IDC0603I CONNECT FOR USER CATALOG USERCAT.Z25D.PRODS SUCCESSFUL
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
When I do a LISTCAT of the master catalog I see this usercat listed:
LISTCAT NAME CAT(CATALOG.Z24D.MASTER)
USERCATALOG --- USERCAT.Z24D.CICS550
USERCATALOG --- USERCAT.Z24D.CICS560
USERCATALOG --- USERCAT.Z24D.DB2VB
USERCATALOG --- USERCAT.Z24D.DB2VC
USERCATALOG --- USERCAT.Z24D.IMS14
USERCATALOG --- USERCAT.Z24D.IMS15
USERCATALOG --- USERCAT.Z24D.INM14
USERCATALOG --- USERCAT.Z24D.PRODS
USERCATALOG --- USERCAT.Z24D.USER
USERCATALOG --- USERCAT.Z24D.WAS900
USERCATALOG --- USERCAT.Z24D.ZMS120
USERCATALOG --- USERCAT.Z25D.PRODS
But when I try to list the usercat I get:
LISTCAT CATALOG('USERCAT.Z25D.PRODS')
IDCAMS SYSTEM SERVICES
LISTING FROM CATALOG -- USERCAT.Z25D.PRODS
IDC3016I CATALOG IS NOT AVAILABLE
IDC3009I ** VSAM CATALOG RETURN CODE IS 4 - REASON CODE IS IGG0CLAH-108
Any idea what I have done wrong and is there a way to get access to this usercatalog? |
|
| Back to top |
|
 |
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
searching for "IDC3009I site:ibm.com"
reveals reason code 108:
| Quote: |
Explanation: A necessary catalog could not be dynamically allocated in the catalog address space, and the catalog parameter list indicated dynamic allocation in the callers address space was not allowed.
Programmer Response: Check for allocation problem determination messages in the job stream output. Follow the programmer response for these messages. |
Are there any other messages in your job or syslog? |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1255
Location: Bamberg, Germany
|
|
|
|
| You seem to have a different MCAT active than CATALOG.Z24D.MASTER, right? |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| Joerg.Findeisen wrote: |
| You seem to have a different MCAT active than CATALOG.Z24D.MASTER, right? |
In the system log at the begining of IPL I see:
IOS128I IPL DEVICE: 00A80 VOLUME: D4RES1
IEA370I MASTER CATALOG SELECTED IS CATALOG.Z24D.MASTER
How can I verify what is the actual master catalog if it is not
'CATALOG.Z24D.MASTER' ? |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1255
Location: Bamberg, Germany
|
|
|
|
See for ex:
| Code: |
LISTC UCAT
1IDCAMS SYSTEM SERVICES TIME ..
- LISTING FROM CATALOG -- MCAT.SY1.ENVA
0USERCATALOG --- ..
0USERCATALOG --- ..
0USERCATALOG --- ..
0USERCATALOG --- ..
|
I assume your imported Catalog might not be listed here. |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| Joerg.Findeisen wrote: |
See for ex:
| Code: |
LISTC UCAT
1IDCAMS SYSTEM SERVICES TIME ..
- LISTING FROM CATALOG -- MCAT.SY1.ENVA
0USERCATALOG --- ..
0USERCATALOG --- ..
0USERCATALOG --- ..
0USERCATALOG --- ..
|
I assume your imported Catalog might not be listed here. |
Here is the output.
LISTCAT UCAT
IDCAMS SYSTEM SERVICES TIME:
LISTING FROM CATALOG -- CATALOG.Z24D.MASTER
USERCATALOG --- USERCAT.Z24D.CICS550
USERCATALOG --- USERCAT.Z24D.CICS560
USERCATALOG --- USERCAT.Z24D.DB2VB
USERCATALOG --- USERCAT.Z24D.DB2VC
USERCATALOG --- USERCAT.Z24D.IMS14
USERCATALOG --- USERCAT.Z24D.IMS15
USERCATALOG --- USERCAT.Z24D.INM14
USERCATALOG --- USERCAT.Z24D.PRODS
USERCATALOG --- USERCAT.Z24D.USER
USERCATALOG --- USERCAT.Z24D.WAS900
USERCATALOG --- USERCAT.Z24D.ZMS120
USERCATALOG --- USERCAT.Z25D.PRODS
The last one is the one I am trying to access. |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1255
Location: Bamberg, Germany
|
|
|
|
| That means within the 2 level structure it should be available. Please try the LISTC CAT(USERCAT.Z25D.PRODS) in Batch mode. Even a LISTC UCAT ALL might help. |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| Joerg.Findeisen wrote: |
| That means within the 2 level structure it should be available. Please try the LISTC CAT(USERCAT.Z25D.PRODS) in Batch mode. Even a LISTC UCAT ALL might help. |
Output of "LISTCAT CATALOG(USERCAT.Z25D.PRODS)" was included in first post.
In the output of "LISTC UCAT ALL" I found something interesting.
USERCATALOG --- USERCAT.Z24D.PRODS
HISTORY
RELEASE----------------2
ENCRYPTIONDATA
DATA SET ENCRYPTION-----(NO)
VOLUMES
IDCAMS SYSTEM SERVICES
LISTING
VOLSER------------D4SYS1
ASSOCIATIONS
ALIAS----NFS
ALIAS----MVS
USERCATALOG --- USERCAT.Z25D.PRODS
HISTORY
RELEASE----------------2
ENCRYPTIONDATA
DATA SET ENCRYPTION-----(NO)
VOLUMES
VOLSER------------D5PRD1
ASSOCIATIONS--------(NULL)
Seems that the USERCAT.Z24D.PRODS catalog is defined with VOL=D4SYS1 and not D4PRD1
Maybe I need to connect USERCAT.Z25D.PRODS with VOL=D5SYS1 instead of D5PRD1 as I initialy did. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
re: "connect USERCAT.Z25D.PRODS with VOL=D5SYS1 instead of D5PRD1"
Which of those volumes do you actually have mounted? And also verify, using ISPF option 3.4 and specifying the volser, that the catalog is actually on that volume. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
re:
| Code: |
ASSOCIATIONS
ALIAS----NFS
ALIAS----MVS |
Do the data sets on the new volume have the same HLQ as on the existing volume? I am not familiar with having two user catalogs for the same HLQ.
Perhaps you should do:
DEFINE NONVSAM for non-VSAM data sets
and DEFINE VSAM... RECAT for VSAM clusters.
so that the new data sets are cataloged in the old user catalog, allowing access to both at the same time. IMHO, this might open a whole new set of problems. |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| Pedro wrote: |
re:
| Code: |
ASSOCIATIONS
ALIAS----NFS
ALIAS----MVS |
Do the data sets on the new volume have the same HLQ as on the existing volume? I am not familiar with having two user catalogs for the same HLQ.
Perhaps you should do:
DEFINE NONVSAM for non-VSAM data sets
and DEFINE VSAM... RECAT for VSAM clusters.
so that the new data sets are cataloged in the old user catalog, allowing access to both at the same time. IMHO, this might open a whole new set of problems. |
I only have problem accessing VSAM clusters on the new volume. The non VSAM ones I can catlog them eaely via ISPF 3.4.
In order to do "DEFINE VSAM... RECAT", do I need to know the cluster attributes as they were defined to VSAM originally ? |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 712
Location: Denmark
|
|
|
|
"In order to do "DEFINE VSAM... RECAT", do I need to know the cluster attributes as they were defined to VSAM originally ?"
Only the cluster type INDEXED | NONINDEXED | NUMBERED | LINEAR should be neccessary.
"How can I verify what is the actual master catalog"
I normally just do a listcat of SYS1.PARMLIB as that is always around adn cataloged in the mastercat. |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| Willy Jensen wrote: |
"In order to do "DEFINE VSAM... RECAT", do I need to know the cluster attributes as they were defined to VSAM originally ?"
Only the cluster type INDEXED | NONINDEXED | NUMBERED | LINEAR should be neccessary.
"How can I verify what is the actual master catalog"
I normally just do a listcat of SYS1.PARMLIB as that is always around adn cataloged in the mastercat. |
This finally worked for me:
IMPORT -
OBJECTS -
((USERCAT.Z25D.PRODS -
VOLUME(D5SYS1) -
DEVICETYPE(3390))) -
CONNECT -
CATALOG(CATALOG.Z24D.MASTER)
DEF PATH -
(NAME(DANIZ25.IGY640.ZFS) -
PATHENTRY( IGY640.ZFS ) -
) -
CATALOG( USERCAT.Z25D.PRODS )
DEFINE ALIAS (NAME(DANIZ25) RELATE('USERCAT.Z25D.PRODS'))
Now I can access 'IGY640.ZFS' via the 'DANIZ25.IGY640.ZFS' path bane |
|
| Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 2023
Location: USA
|
|
|
|
Please, be polite to your potential readers. Learn this.
| danik56 wrote: |
This finally worked for me:
| Code: |
IMPORT -
OBJECTS -
((USERCAT.Z25D.PRODS -
VOLUME(D5SYS1) -
DEVICETYPE(3390))) -
CONNECT -
CATALOG(CATALOG.Z24D.MASTER)
DEF PATH -
(NAME(DANIZ25.IGY640.ZFS) -
PATHENTRY( IGY640.ZFS ) -
) -
CATALOG( USERCAT.Z25D.PRODS )
DEFINE ALIAS (NAME(DANIZ25) RELATE('USERCAT.Z25D.PRODS')) |
Now I can access 'IGY640.ZFS' via the 'DANIZ25.IGY640.ZFS' path bane |
|
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| sergeyken wrote: |
Please, be polite to your potential readers. Learn this.
| danik56 wrote: |
This finally worked for me:
| Code: |
IMPORT -
OBJECTS -
((USERCAT.Z25D.PRODS -
VOLUME(D5SYS1) -
DEVICETYPE(3390))) -
CONNECT -
CATALOG(CATALOG.Z24D.MASTER)
DEF PATH -
(NAME(DANIZ25.IGY640.ZFS) -
PATHENTRY( IGY640.ZFS ) -
) -
CATALOG( USERCAT.Z25D.PRODS )
DEFINE ALIAS (NAME(DANIZ25) RELATE('USERCAT.Z25D.PRODS')) |
Now I can access 'IGY640.ZFS' via the 'DANIZ25.IGY640.ZFS' path bane |
|
I'll be happy to learn how this was done.... |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 582
Location: London
|
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
When mounting READ-ONLY ? |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 582
Location: London
|
|
|
|
Not sure, I only remembered seeing the entry I posted the link for. It doesn't saying in there if it relates to READ only.
Here's the full content from the link:
When we create an IDCAMS PATH on a zFS, although the IBM documentation says "DON'T DO IT" , it is still allowed.
Plus, zFS allows a PATH to be mounted on mountpoint A while you can still mounthe real zFS to mountpoint B, which lead to corrupt our zFS , and the salvage did not correct the situation .
: Do not use a path entry as the file system name in the MOUNT command. For more information, see
DEFINE PATH in z/OS DFSMS Access Method Services Commands. The mount succeeds but the system
issues messages similar to the following ones: |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1255
Location: Bamberg, Germany
|
|
|
|
| Same in our shop, no more PATHs for z/FS. It helped to solve problems with backup from DFHSM. |
|
| Back to top |
|
|
|
|
