Re: zCX Provisioning Problem
These are job streams that are automatically created by the workflow provisioning. I have had no hand in creating the contents of them. So I would've expected that they'd "just work". This is the information provided with the ADCD z/OS 2.4 May Edition: "The data class CXDC is defined to allow larger than four Gigabyte dataset allocation. With this data class and the accompanying storage group and class, a dataset can be allocated on the provided SMS managed volume D4ZCX1. The ACS routines are used during provisioning of zCX Container." Data class Storage Group and Storage class for zCX Containers reference purposes: CXDC - Data Class for zCX CXROOTSG - Storage Group CXROOTSC - Storage class D4ZCX1 - Volume size is 18,000 cylinders and defined in CXROOTSG (Storage Group) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: zCX Provisioning Problem
I USER a catalog alias? What is the definition of CXROOTSC? What do your ACS rules do with USER.ZCX.SNAZCX.ZFS? "80 Explanation:Define data set with extended format information is not valid for a non-SMS data set." BTW, do you really mean "(3)" and not "(3 3)"? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Neale Ferguson [ne...@sinenomine.net] Sent: Tuesday, November 30, 2021 4:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: zCX Provisioning Problem I am attempting to run the zCX provisioning workflow. It gets to the step where it allocates then mounts a ZFS system. However, the DEFINE CLUSTER is failing using: DEFINE CLUSTER - (NAME(USER.ZCX.SNAZCX.ZFS) - MEGABYTES(4095 1000) - STORCLAS(CXROOTSC) - DATACLAS(CXDC) - ZFS - SHAREOPTIONS(3)) It fails with: IDC3506I REQUIRED VOLUMES AND/OR DEVICETYPES HAVE BEEN OMITTED IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 If I change the DEFINE to include a VOL() definition: DEFINE CLUSTER - (NAME(USER.ZCX.SNAZCX.ZFS) - MEGABYTES(4095 1000) - STORCLAS(CXROOTSC) - DATACLAS(CXDC) – VOL(D4ZCX1) - ZFS - SHAREOPTIONS(3)) It fails with: IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80 I am unable to work out what IGG0CLAT-80 is or why it’s failing. I am unsure why VOL is required anyway, wouldn’t the STORCLAS/DATACLAS let the system pick for itself? Might that volume not have enough free space? I would’ve hoped that the generated workflow would “just work” with the right parameters. So I assume one of my parameter is wrong but I didn’t see anywhere I could plug in a volume name into the workflow parameters. Neale -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: zCX Provisioning Problem
On Tue, 30 Nov 2021 05:54:25 -0600, Dave Jousma wrote: >On Tue, 30 Nov 2021 09:43:55 +, Neale Ferguson >wrote: > > >>It fails with: >> >>IDC3014I CATALOG ERROR >>IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80 >> >>I am unable to work out what IGG0CLAT-80 is or why it’s failing. I am unsure >>why VOL is required anyway, wouldn’t the STORCLAS/DATACLAS let the system >>pick for itself? Might that volume not have enough free space? I would’ve >>hoped that the generated workflow would “just work” with the right >>parameters. So I assume one of my parameter is wrong but I didn’t see >>anywhere I could plug in a volume name into the workflow parameters. >> > >80 Explanation: Define data set with extended format > information is not valid for a non-SMS data set. Does your dataclass specify extended format? Or reduce your dataset allocation to something less than 65K tracks and try it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: zCX Provisioning Problem
On Tue, 30 Nov 2021 09:43:55 +, Neale Ferguson wrote: >It fails with: > >IDC3014I CATALOG ERROR >IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80 > >I am unable to work out what IGG0CLAT-80 is or why it’s failing. I am unsure >why VOL is required anyway, wouldn’t the STORCLAS/DATACLAS let the system pick >for itself? Might that volume not have enough free space? I would’ve hoped >that the generated workflow would “just work” with the right parameters. So I >assume one of my parameter is wrong but I didn’t see anywhere I could plug in >a volume name into the workflow parameters. > 80 Explanation: Define data set with extended format information is not valid for a non-SMS data set. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
zCX Provisioning Problem
I am attempting to run the zCX provisioning workflow. It gets to the step where it allocates then mounts a ZFS system. However, the DEFINE CLUSTER is failing using: DEFINE CLUSTER - (NAME(USER.ZCX.SNAZCX.ZFS) - MEGABYTES(4095 1000) - STORCLAS(CXROOTSC) - DATACLAS(CXDC) - ZFS - SHAREOPTIONS(3)) It fails with: IDC3506I REQUIRED VOLUMES AND/OR DEVICETYPES HAVE BEEN OMITTED IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 If I change the DEFINE to include a VOL() definition: DEFINE CLUSTER - (NAME(USER.ZCX.SNAZCX.ZFS) - MEGABYTES(4095 1000) - STORCLAS(CXROOTSC) - DATACLAS(CXDC) – VOL(D4ZCX1) - ZFS - SHAREOPTIONS(3)) It fails with: IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80 I am unable to work out what IGG0CLAT-80 is or why it’s failing. I am unsure why VOL is required anyway, wouldn’t the STORCLAS/DATACLAS let the system pick for itself? Might that volume not have enough free space? I would’ve hoped that the generated workflow would “just work” with the right parameters. So I assume one of my parameter is wrong but I didn’t see anywhere I could plug in a volume name into the workflow parameters. Neale -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
