Creating AWS file from dataset on tape

Hi, I would like to create AWS files from datasets on tape. I found the AWSSL program on file 585 on the CBT. This program can create AWS files, but cannot read files on tape. There are also some program in file 533 that are named VTT2. Can these files be used to read a tape file, by name,

Re: How the determine dataset is PDSE

Like this, I'd say. ... MVC ISITM_W(ISITM_L),ISITM_C ISITMGD DCB=DCB1,MF=(E,ISITM_W) USING ISM,R1 STR15,ISIT_RC SAVE RETURN CODE STR0,ISIT_RSN SAVE REASON CODE LTR R15,R15 ISTSMGD OK?

Re: Issues while compiling SVC exit on Z1.10

From the JSE2 Macro Reference: Table 8. JES2 DSECTIDs That Can Be Specified on $MODULE (continued) DSECTID MacrosDescription of Code Generated $BFW $BFW 3800 buffer work area DSECT $BLDMSGL$BLDMBuild message parameter list DSECT $BTG $BTG

Re: Unicode services Red alert

>What bugs me is that z/OS 1.13 systems are not exposed >to this defect yet IBM created an aparfix for 1.13. Any application, whether customer-owned, ISV-owned, or IBM-owned could be using this service (which has been in z/OS since z/OS 1.10). IBM has no idea what might fit into those first

Re: Unicode services Red alert

So far we have the APAR, Any idea when we will be getting the GA PTF for this ? On Thu, Oct 8, 2015 at 8:08 PM, Peter Relson wrote: > >What bugs me is that z/OS 1.13 systems are not exposed > >to this defect yet IBM created an aparfix for 1.13. > > Any application, whether

IOEZ00807I when OMVS initializes at Disaster Recovery site

Searched the archives and saw others had this issue, but never saw a good answer. We recently implemented ZFS file sharing for the first time here. We run GDPS/XRC to replicate our dasd from HQ to DR site and then often "flash" the farm to a set we can IPL our recovery system from. Because

Re: Issues while compiling SVC exit on Z1.10

On 8 October 2015 at 00:47, Rakesh Kotha <00cf1d6d10e9-dmarc-requ...@listserv.ua.edu> wrote: > 10 0 11229+ L R15,C@$MSDDUMP-CADDR(R15, > ** ASMA044E Undefined symbol - C@$MSDDUMP > ** ASMA044E Undefined symbol - CADDR > ** ASMA435I Record 1256 in SYS1.SHASMAC($HCCT) on

Re: Unicode services Red alert

I was told, by our IBM person, that the official PTF we be made available on October 16th. Gadi From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jake Anderson [justmainfra...@gmail.com] Sent: 08 October 2015 17:46 To:

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

Most operating system files are r/o. But it is impossible to do that at the live site with the majority of our ZFS files. And we have over 200 ZFS files. Thanks, Dave On Thu, Oct 8, 2015 at 10:55 AM, wrote: > Hi Dave, > > Keep all your system ZFS r/o at the live

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

Seems like they should be able to create a BPX parm to tell OMVS to ignore the check. Very frustrating. We may need to pursue mounting just what we need to IPL to a base level, and mount the rest after as you suggest. Thanks, Dave

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

On Thu, 8 Oct 2015 11:21:09 -0500, Dave Butts wrote: >Seems like they should be able to create a BPX parm to tell OMVS to ignore the >check. >Very frustrating. >We may need to pursue mounting just what we need to IPL to a base level, and >mount the rest after as you

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

We have the same issue (more than 2 hours). I've asked IBM about this in the past and didn't get much of an answer besides WAD. I've considered taking the application specific mounts out of BPXPRMxx and mount them after the system is up. Maybe make it part of the application startup in System

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

Maybe you could go to DeveloperWorks and explain to IBM via an RFE the benefits of a process to ignore integrity at DR. Or provide a way at DR to tell zFS to do something else. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

Dave, I looked back through the PMR I opened on this and one comment IBM made was that you will not incur the 65 second wait penalty if the system and plex names at recovery time are the same as what's in block zero. I've never tested this since we can't predict/determine what system owned the

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

We use the following setup to circumvent this to some degree: We start OMVS with parms of (TH,FS,ZS) BPXPRMTH contains the Threshold values etc. BPXPRMFS contains the FileSystem definitions - ZFS, CINET etc. BPXPRMZS contains the mounts for those ZFS datasets supplied as part of z/OS - no

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

Agreed. We will be pursuing opening a request to IBM for sure. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

Thanks, Bart. In my pmr with IBM, they confirmed that ensuring those match are not enough to guarantee it will avoid the wait. Here is what IBM told us: -- Just finished discussing this with my defect folks and unfortunately using the same SYSNAME and SYSPLEX name on the

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

I submitted my vote for the RFE. --- dbutt...@gmail.com wrote: From: Dave Butts To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IOEZ00807I when OMVS initializes at Disaster Recovery site Date: Thu, 8 Oct 2015 14:12:57 -0500 Thanks, Bart. In my pmr

Re: Subscribing to IBM-MAIN

Darren will probably respond when he gets off his day job. Guess the answer is required. If they're still having trouble might try the web page at listserv.ua.edu/archives/ibm-main.html where you can sign up and set options for sending and receiving. In a message dated 10/8/2015 3:49:56

Re: Subscribing to IBM-MAIN

When I subscribed last year I didn't code any firstname or lastname, but the response email indicated my name which it must have grabbed from my "From" address. Here's the source of my request, if that helps at all. From - Sat Sep 13 23:32:27 2014 X-Mozilla-Status: 0001 X-Mozilla-Status2:

Subscribing to IBM-MAIN

Two of my colleagues are trying to join IBM-MAIN. Neither one is successful. Both have sent notes to LISTSERV trying to following the INFO directive: SUBSCRIBE IBM-MAIN What's with the angle brackets? Required? Prohibited? Nothing seems to work. . . . J.O.Skip Robinson Southern California

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

I made this comment on the RFE. Perhaps it should be a new RFE. For the MOUNT command and in SYS1.PARMLIB(BPXPRMxx), add a NOWAIT and / or DEFER keywords.For a NOWAIT keyword begin the files system check that could take 65 seconds.For a DEFER keyword wait until an access of the file

Re: Subscribing to IBM-MAIN

Don't use the angle brackets. It's just notation - -teD -   Original Message   From: Ed Finnell Sent: Thursday, October 8, 2015 18:20 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: Subscribing to IBM-MAIN Darren will probably respond when he gets off his day

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

In , on 10/08/2015 at 03:14 PM, Mike Schwab said: >I made this comment on the RFE. Perhaps it should be a new RFE. >For the MOUNT command and in SYS1.PARMLIB(BPXPRMxx), add a NOWAIT and >/ or DEFER

Re: Subscribing to IBM-MAIN

That is correct. If you provide a proper From: address nothing else is required. In a message dated 10/8/2015 5:47:16 P.M. Central Daylight Time, t...@tombrennansoftware.com writes: When I subscribed last year I didn't code any firstname or lastname, but the response email indicated my

Re: File Placement Utility

On Fri, 9 Oct 2015 01:25:00 +, Hardee, Chuck H. wrote: >I have a need to juggle the locations of 1500+ files on 70 volumes. >These packs are not SMS managed and will never be. >There will be 4 sets of these files across 4 sets of 70 DASD volumes. > Oooh! The Knapsack Problem:

Re: File Placement Utility

> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Hardee, Chuck H. > Sent: Thursday, October 08, 2015 6:25 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: File Placement Utility > > I have a need to juggle the locations of 1500+ files

File Placement Utility

I have a need to juggle the locations of 1500+ files on 70 volumes. These packs are not SMS managed and will never be. There will be 4 sets of these files across 4 sets of 70 DASD volumes. Does anyone know of a utility, REXX, EXCEL, executable program, etc, that would let me feed in the file

Re: File Placement Utility

Calculate the number of total number of tracks. Divide by number of volumes, result is how many tracks to use on each volume. Init n-1 volumes with small VTOC, one with a larger VTOC for lots of small files. Sort by descending number of tracks. Move largest remaining file to the volume with small

Re: File Placement Utility

Why not just use ADRDSSU, something like COPY DATASET( - INCLUDE( - Your list of datasets - ) - ) - OUTDY( - (yourxx target fourxx

Re: File Placement Utility

Here is what I do (when copying prod to QA files) - there might be easier or better ways - but this is the best I came up with, with my limited mental resources . Get the name and size (# of tracks) of each of the 1500+ files (we use CA-RSVP) Sort by size (descending) Then write a

Re: IOEZ00807I when OMVS initializes at Disaster Recovery site

We converted to sysplex shared filesystems, and this issue went away. We recover our DR system almost weekly, and that 65 second delay is a real PITA. _ Dave Jousma Assistant Vice President, Mainframe Engineering