Re: APF problem

On Sun, 18 Feb 2018 03:44:52 + Jesse 1 Robinson wrote: :>I've been doing this for so many years that I thought I could not be stumped by an APF problem. I get a SD22-20, which I had to look up: :>D22-20 :>The program is not authorized to issue the MGCR or MGCRE

Re: APF problem

I think the key is the “and” between supervisor state and psw key 0-7. Try MODESET KEY=ZERO,MODE=SUP DAN On Feb 17, 2018, 22:45 -0500, Jesse 1 Robinson , wrote: > I've been doing this for so many years that I thought I could not be stumped > by an APF problem. I get a

APF problem

I've been doing this for so many years that I thought I could not be stumped by an APF problem. I get a SD22-20, which I had to look up: D22-20 The program is not authorized to issue the MGCR or MGCRE macro. The program must be in supervisor state and PSW key 0-7. Here's the relevant code: *

Re: SMS dataset oddity with COM-Plete

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.idas200/rovars.htm Check what you handle in your ACS Storage Group routine for the affected DSNs (Filter list, mask). Normal creation (DISP=NEW) is ALLOC. Your batch move job could be RECALL, RECOVER, or RENAME. On

Re: SMS dataset oddity with COM-Plete

No, the volumes are identical (same raid, same channels, etc.) except that the one (that results in an s0C1) is in an SMS pool and the other is not. The data got to the pool because we sent it there via a dfdss batch job to move all of the development datasets to a "new" 48 volume development

Re: SMS dataset oddity with COM-Plete

Vendor's technical support would be an idea to consider. Otherwise what else is unique about the "target" DASD volume, possibly EAV/EAS type (though consider you mentioned 3390-3) - inquire with Stg Mgmt for additional insight on DASD environment consideration. Sometimes a simple TSO ISPF

AW: SMS dataset oddity with COM-Plete

Not knowing Com-Plete, I can only guess: Edit/Browse might use NOTE and POINT, do they? These services work with the TTR of the records on the disk. For this to work with SMS managed data sets, they need to be EXTENDED format data sets. In a previous job I was working with some home written

Re: SMS dataset oddity with COM-Plete

I'm thinking you need to update the ACS routines for when a dataset is reallocated or recalled from ML1/2. Didn't code it myself so very hazy on the details. On Fri, Feb 16, 2018 at 8:47 PM, Brian Westerman wrote: > Hi, > > One of our customers is running an