In the past when I used linear I also had to format it with
//FORMATFS EXEC   PGM=IOEAGFMT,REGION=0M,COND=(0,NE,DEFINE),
// PARM=('-aggregate COLIN.ZOPEN.ZFS  ')
//*  PARM=('-aggregate COLIN.ZOPEN.ZFS    -compat')
//SYSPRINT DD     SYSOUT=*
//STDOUT   DD     SYSOUT=*
//STDERR   DD     SYSOUT=*
Then it would mount
Are you saying the IDCAMS define .. ZFS does the format for you?
Colin

On Fri, 24 Oct 2025 at 17:23, Mark Jacobs <
[email protected]> wrote:

>     DEFINE CLUSTER (NAME(A2MJAET.TEST.ZFS) -
>
>            CYL(1 1)  SHAREOPTIONS(3) LINEAR)
>
> IGD01009I ACSMC02W DATASET HAS BEEN ALLOCATED WITH STD0 MANAGEMENT CLASS
> IGD01009I MSG07    MANAGEMENT CLASS ASSIGNED STD0
> IGD17070I DATA SET A2MJAET.TEST.ZFS
> ALLOCATED SUCCESSFULLY WITH 1 STRIPE(S).
> IGD17172I DATA SET A2MJAET.TEST.ZFS
> IS ELIGIBLE FOR EXTENDED ADDRESSABILITY
> IDC0508I DATA ALLOCATION STATUS FOR VOLUME ITFA1H IS 0\
> IDC0512I NAME GENERATED-(D) A2MJAET.TEST.ZFS.DATA
> IDC0181I STORAGECLASS USED IS S1
> IDC0181I MANAGEMENTCLASS USED IS STD0
> IDC0181I DATACLASS USED IS EAVSAM
>
> IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
>
> IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0
>
> mount filesystem('A2MJAET.TEST.ZFS') mountpoint('/u/A2MJAET/mount')
> type(zfs)
>
> BPXF135E RETURN CODE 00000079, REASON CODE EF016C54.  THE MOUNT FAILED FOR
> FILE
>
> SYSTEM A2MJAET.TEST.ZFS.
>
> zFS Mon Oct 28 19:01:32 EDT 2024
>
> Description: The VSAM LDS is not formatted, is not marked as intended for
> zFS,
>
> and cannot be formatted at mount.
>
> Action: Format the VSAM LDS using the zfsadm format command and try the
> mount
>
> again.
>
>
>
> Sent from ProtonMail, Swiss-based encrypted email.
>
> GPG Public Key -
> https://api.protonmail.ch/pks/lookup?op=get&[email protected]
>
>
> On Friday, October 24th, 2025 at 12:13 PM, Jousma, David <
> [email protected]> wrote:
>
> > Mark,
> >
> > This is not true. Just ran this today
> >
> > DEFINE CLUSTER(NAME(OMVSU.TEC1.DB2AAAS.SERVICE) -
> > LINEAR -
> > STORCLAS(SCSYSTEM) -
> > MB(500) SHAREOPTIONS(3,3))
> >
> >
> > _______________________________
> >
> > Dave Jousma
> >
> > Vice President | Director, Technology Engineering
> >
> > Fifth Third Bank | 1830 East Paris Ave, SE | Grand Rapids, MI 49546
> >
> >
> >
> >
> >
> >
> > From: IBM Mainframe Discussion List [email protected] on behalf
> of Mark Jacobs [email protected]
> >
> > Date: Friday, October 24, 2025 at 12:05 PM
> > To: [email protected] [email protected]
> >
> > Subject: Re: Configuring ZFS data sets
> >
> > CAUTION EXTERNAL EMAIL
> > This message came from outside your organization.
> > DO NOT open attachments or click on links from unknown senders or
> unexpected emails.
> > Report Suspicioushttps://
> us-phishalarm-ewt.proofpoint.com/EWT/v1/MwwqYLOC6b6whF7V!pHOFdhTiQyxKmg4Sp3Khl3g01dPae3MCOKFTSygwHwVMMJldFfDtH8cHbZCBsgYxyEXY-pNuyHr4hrYm0DzxrDU_kZCccsCs-rpIrbKAl8YXv-8pqDzqEs_GHBP97QbilUmeSx3JT0tI6fAM7204m2hSpfbR-6-RdL9PEUyaTTCv7jQNBsCPvNqxDlRsaBJsG5Ct_2MmfQ$
> >
> >
> >
> > Using LINEAR won't work. You need to specify ZFS if you use IDCAMS to
> define a zfs file system. Your template JCL is the older/original method of
> defining a ZFS file system. It still works, but IDCAMS IMHO is easier.
> >
> > Mark Jacobs
> >
> > Sent from ProtonMail, Swiss-based encrypted email.
> >
> > GPG Public Key -
> https://urldefense.com/v3/__https://api.protonmail.ch/pks/lookup?op=get&[email protected]__;!!MwwqYLOC6b6whF7V!jj7sDnkR1VbeVWs3xMbs0oaynKGHtpHNyinibMu7S8iVyZTy3_rMiz0hwgrx6hFnjmYx0qH6XXbCu6JRqw7wfPvaMi1gu72LVoc$
> >
> >
> > On Friday, October 24th, 2025 at 11:46 AM, Colin Paice
> [email protected] wrote:
> >
> > > I'm about to set up some new ZFS data sets
> > > Is there any guidance on the best way of doing it?
> > > - My DEFINE cluster has LINEAR - but I see there is a ZFS option. Does
> it
> > > really make a difference?
> > > - My template JCL has "-compat" in it. Is this recommended ?
> > > Are there any performance options I should be enabling?
> > > Colin
> > >
> > > ----------------------------------------------------------------------
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to [email protected] with the message: INFO IBM-MAIN
> >
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
> >
> >
> >
> > This e-mail transmission contains information that is confidential and
> may be privileged. It is intended only for the addressee(s) named above. If
> you receive this e-mail in error, please do not read, copy or disseminate
> it in any manner. If you are not the intended recipient, any disclosure,
> copying, distribution or use of the contents of this information is
> prohibited. Please reply to the message immediately by informing the sender
> that the message was misdirected. After replying, please erase it from your
> computer system. Your assistance in correcting this error is appreciated.
> >
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to