IBM wheels out bleedin' big 15TB tape drive Proprietary tape format bits shrink while capacity bulks up

> http://www.theregister.co.uk/2017/05/11/ibm_15tb_tape_drive/ > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: AUTOIPL SADUMP LOADPARM flag value

On 5/12/2017 5:18 PM, Jesse 1 Robinson wrote: It's Friday, so I can (re)tell my war story. Shortly after z/OS R13 hit our first prod system, I noticed one morning that the system had been IPLed around 05:00. Everyone denied having done it. Then I discovered a fresh SAD taken around the same

Re: AUTOIPL SADUMP LOADPARM flag value

It's Friday, so I can (re)tell my war story. Shortly after z/OS R13 hit our first prod system, I noticed one morning that the system had been IPLed around 05:00. Everyone denied having done it. Then I discovered a fresh SAD taken around the same time. Sent if off to IBM. Next day or two, the

Re: AUTOIPL SADUMP LOADPARM flag value

On Fri, 12 May 2017 16:18:14 +, Jesse 1 Robinson wrote: >I'm curious as to why you do not want automatic reIPL after SADMP. Your >system is in a non-restartable wait state, after all. I view that as the >ultimate performance degradation. ;-) You have an

AW: Re: How to find Cobol (and C) Working Storage variables in an SVCDUMP

>> Interesting. A reference to _gtca() also in LE Vendor Interfaces. Hints here >> and there in the C/C++ docs. > I suspect _gtca() does something similar to what is described in "Chapter 14. > Anchor support" in the LE Vendor Interfaces manual. Out of curiosity, I had a look at CEEARLU.

Re: AUTOIPL SADUMP LOADPARM flag value

I'm curious as to why you do not want automatic reIPL after SADMP. Your system is in a non-restartable wait state, after all. I view that as the ultimate performance degradation. ;-) You have an SAD. If want to look at it or at OPERLOG, you need at least one system in the sysplex up and

Re: How to find Cobol (and C) Working Storage variables in an SVCDUMP

On Thu, 11 May 2017 17:08:41 -0500, John McKown wrote: > STM R0,RF,12(RD) SAVE ALL REGS. > L R3,0(,R1) POINT TO RETURN AREA > ​MVC 0(64,R3),12(RD) MOVE REGS AT ENTRY > SLR RF,RF > BR RE > >This does not use standard linkage, but is that really necessary? You are going to

Re: AW: Re: job output into dataset

Hello Lizette, Thanks for reply. I will add JESLOG=SPIN in my proc. But one of my query still answered that do we need to recycle address space after changing STC class outdisp paramter to write,write to make this spin work . Or can we do it dynamically without shutting down address space. On

Re: rename datasets

The TMC has two fields. Full tape dataset name And a second field that contains the last 17 characters. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Paul Gilmartin > Sent: Thursday, May 11, 2017 9:36 AM > To:

Re: AW: Re: job output into dataset

So the best option would be to do 1) Check the STC in the JES2 Class and see if JESLOG=SPIN is included. 2) Start the STC with the SPIN Option JESLOG= Specifies for the indicated jobclass that each job's JESLOG data (JESMSGLG and JESYSMSG data sets) is to be spun at a certain time

Re: AUTOIPL SADUMP LOADPARM flag value

Hello Jim, thank you. summary:- SADUMP treats last LOADPARM character as if it is a hexadecimal nibble. 1... 8 - reserved for IBM - do not use .1.. 4 - SADUMP will attempt re-ipl using stored DIAG member MVS() parameter values ..1. 2 - unassigned - do not use ...1 1

Re: rename datasets

>we are looking at renaming all of the datasets like the below. > >Old dataset - > SLXR5V.SAPDB.* >New dataset - > SLXR5V.SAPDB.X.* Something that nobody had mentionesd so far: A rename will *not* move that data set to some other storage group. I.e. while a rename will drive ACS routines,