My problem with being able to access an uncataloged dataset may be SMS
related
To test this out, I have an edit macro
*/* REXX */ address isredit TRACE R 'MACRO (a) ' address
ispexec "edit dataset('COLIN.MIG.JCL') VOLUME(USER02)" *
Executing this gives me
*ISRD014 Data set not
cataloged 'COLIN.MIG.JCL' was not found in
catalog. Current dialog
statement:edit dataset('COLIN.MIG.JCL') VOLUME(USER02)*
Once I import the user catalog, and define the alias I can use the data
set. "I" gives
* Data Set Name . . . . : COLIN.MIG.JCL *
*
General Data Current Allocation
Management class . . : **None** Allocated cylinders : 1 Storage
class . . . : SCBASE Allocated extents . : 1 Volume serial . . .
: USER02 Maximum dir. blocks : NOLIMIT Device type . . . . : 3390
Data class . . . . . :
**None** ... Data set
name type : LIBRARY Dates Data set
encryption : NO Creation date . . . : 2024/01/14 Data set
version . : 2 Referenced date . . : 2024/07/28
Expiration date . . : ***None*** SMS
Compressible . : NO *
This is SMS managed
___________________________________________
A dataset which does work has
*Data Set Name . . . : USER.Z24A.PROCLIB
General
Data Current Allocation Volume
serial . . . : A4CFG1 Allocated cylinders : 10 Device type . . . .
: 3390 Allocated extents . : 1 Organization . . . : PO
Maximum dir. blocks : 20 Record format . . . : FB
Record length . . . : 80
Block size . . . . : 6160 Current
Utilization 1st extent cylinders: 10 Used
cylinders . . : 6 Secondary cylinders : 10 Used extents . .
. : 1 Data set encryption : NO Used dir. blocks . : 10
Number of members . : 65*
This is not SMS managed.
Strange eh!
Colin
On Sun, 28 Jul 2024 at 05:49, Brian Westerman <
[email protected]> wrote:
> If the dataset is SMS managed and the dataset is not cataloged in your
> current catalog structure, you can't edit it without specifying the
> volser.
>
> For instance, if you use 3.4 and display a SMS volume (by volser and not
> displaying by HLQ), and try to edit a SMS dataset that is not cataloged in
> that current catalog structure, then it will fail with the message you
> saw.
>
> Since it's a new system, possibly you didn't include the catalog that owns
> that dataset's HLQ in your 3.1 catalog structure, i.e. it's in a usercat
> which has not yet been imported into your new master catalog, or you did
> import the catalog, but didn't define the alias as being owned by that
> catalog in your "new" master catalog.
>
> If none of that is changed, then it's probably something simple like you
> need to update your ACS routines to make sure that zos knows that the
> volume is indeed a SMS volume and is part of some "valid" storage group.
> Sometimes people forget that you have to reload or at least catalog your
> SMS ACDS, SCDS and COMMDS for that new system and SMS comes up in null
> configuration mode, sometimes people will change the name of the LPAR
> (because it's new) and forget that their old ACDS doesn't know about that
> LPAR (yet), so it doesn't load the SMS routines and constructs that you
> need for that particular "new" LPAR.
>
> Brian
>
> ----------------------------------------------------------------------
> 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
