Re: MCDS CDS BACKVOL fails

I think that you will find that until you fix the problem with backing up the MCDS, that you won't be able to release the rest of the work that you want HSM to do. Brian -- For IBM-MAIN subscribe / signoff / archive access

Re: Once upon a time......

"Funny you should mention it." On April 5, 2022, IBM announced the IBM z16 with new IBM Telum Processors. Every main processor chip on the IBM z16 is equipped with a new AI accelerator section. Here's the list of operations supported on the AI accelerator: LSTM Activation GRU Activation Fused

Re: System Dump DS's

>That's correct. I didn't delete mine either, I just made them very small. IIRC, the system dump data sets should not be deleted. Dynamic dumps require SMS to be active. Before SMS is active, no dump can be taken when the old-style dump data sets are not available anymore. I remember one

Re: Once upon a time......

Maybe not for zOS, but I personally think Linux on Z (with DPM fully "featured out" for automatic machine management) can be a beast. If only IBM or independent reviewers ran actual comparisons of costs, density, etc. zDNN on z16 chip is "ok", but do note that this is again a whole bunch of

Re: Once upon a time......

Charles wrote, in part: Although, isn't @Dave's idea more or less what IBM has done with AI and the z16? Coupled specialized processors to a Z? >Although, isn't @Dave's idea more or less what IBM has done with AI and the >z16? Coupled specialized processors to a Z? Seems like it, though I'm

Re: MCDS CDS BACKVOL fails

Hi, "MIGRATION, BACKUP, FRBACKUP, DUMP, AND RECYCLE HELD." is not the cause but the result of this error. Even if all function is held, only BACKVOL CDS can be executed. ARC0744E RC=36 says backup version data sets can not be located. Could you pre-allocate all backup version data sets in the

Re: HMC and zombie USB device

Radoslaw Skorupka wrote: >Yes, you are right - there is no logical difference between internal and >external USB port. However I can imagine "whitelisted" internal ports, >because every port has its own ID. Nevermind. >More important is device whitelist Do you really want whitelisting here? I

Re: Once upon a time......

Correction: Just realized the z Decimal Floating point is also based on the IEEE 754 Standard as well, so "IEEE floating point" also includes decimal floating point and encompasses all the Decimal Floating Point formats and arithmetic instructions too.      Joel C. Ewing On 8/21/22 17:29,

Re: Once upon a time......

Actually "IEEE floating point" is rather specific. z-architecture now supports the original Hex Floating Point (HFP) data formats, plus the newer Binary Floating Point (BFP) and Decimal Floating Point (DFP) formats.  BFP is based on IEEE binary floating point standards, and should be

Re: Once upon a time......

The mainframe workload continues to increase and will continue to increase for decades. Sent from Yahoo Mail for iPhone On Sunday, August 21, 2022, 5:29 PM, Charles Mills wrote: You would offload a lot of the (expensive) Z cycles to the GPU, right? Still, I agree, hard for me to see this

Re: IARV64 REQUEST=LIST with V64SELECT=YES,OWNERASID=MYASID returning all asid

The ownerasid seems to refer only to common memory objects ? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Sunday, August 21, 2022 5:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IARV64 REQUEST=LIST with V64SELECT=YES,OWNERASID=MYASID returning

Re: IARV64 REQUEST=LIST with V64SELECT=YES,OWNERASID=MYASID returning all asid

Yes it should only get data back from what I understand OWNERASID= which is X'0021' I got data from other asid's ? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Sunday, August 21, 2022 5:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:

Re: Once upon a time......

You would offload a lot of the (expensive) Z cycles to the GPU, right? Still, I agree, hard for me to see this flying. It pains me to say this, but we just don't seem to hear people saying "I would love to put business process 'X' on the mainframe." Don't flame me -- I love the Z and the

Re: IARV64 REQUEST=LIST with V64SELECT=YES,OWNERASID=MYASID returning all asid

Is this a question? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joseph Reichman Sent: Sunday, August 21, 2022 1:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IARV64 REQUEST=LIST with V64SELECT=YES,OWNERASID=MYASID returning

Re: Once upon a time......

On 8/21/22 12:17 PM, Dave Jones wrote: Now I am wondering if, perhaps, the time is right for IBM to re-consider that decision. On modern z processors, we already have IEEE floating point instructions in the hardware, Linux (a popular options for Intel-base number-crunch systems), and support

Re: Once upon a time......

Dave Jones wrote about attaching GPU cards to a Z to make it a super-number cruncher. What's the problem you're trying to solve? Cheap Intel MIPS being too inexpensive? Seriously, I've never heard anyone say "I'd put this numeric-intensive application on zSystems but they're just too slow".

IARV64 REQUEST=LIST with V64SELECT=YES,OWNERASID=MYASID returning all asid

Hi First I read the documentation so I hope Peter Relson doesn't scream at me Let post my coding of the macro ARV64 REQUEST=LIST, X V64LISTPTR=WRKPTR, X V64SELECT=YES,

Re: Once upon a time......

What gives you that idea? The 7090 and 7094 preceded the S/360, and the supercomputing link from that page lists machines back to 1954. Not that IBM was the only fish in that pond (-; -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM

Re: Once upon a time......

On Sun, 21 Aug 2022 13:17:41 -0500, Dave Jone wrote: >IBM was known for making some really nice scientific number-crunching systems. > > (But almost a decade old.) Does "nice" mean to you "360-compatible"? -- gil

Once upon a time......

IBM was known for making some really nice scientific number-crunching systems. The 7090-7094, the S/360-195 and the follow-on s/370-195, the array processor 3838 and the vector instruction set supported by the 30xx models come to mind. Over time, and with the rise of the Intel-based chips and

Re: rexx and IDCAMS functions

On Sat, 20 Aug 2022 13:28:29 -0700, Lizette Koehler wrote: >I think what I am having a challenge with is the STGADMN.IDC.DCOLLECT in >Facility Class > >The UACC is NONE but the ACL has * READ > >The process creates the JCL Statements in ALLOC statements. SYSIN will >contain the DCOLLECT

Re: EXTERNAL EMAIL: How prohibit one user from one dataset?

> What about JES(BATCHALLRACF)? Can you comment it? Doesn't it work? I don't know about it, to provide useful comments. - KB --- Original Message --- On Sunday, August 21st, 2022 at 6:16 PM, Radoslaw Skorupka wrote: > W dniu 21.08.2022 o 14:09, kekronbekron pisze: > > > > IMHO JES

Re: EXTERNAL EMAIL: How prohibit one user from one dataset?

Sorry, thought it was understood from the context. Unexpected nodes = folks "poking" at the mainframe with their scripts, at the NJE interface. - KB --- Original Message --- On Sunday, August 21st, 2022 at 6:16 PM, Radoslaw Skorupka wrote: > W dniu 21.08.2022 o 14:09, kekronbekron

Re: EXTERNAL EMAIL: How prohibit one user from one dataset?

W dniu 21.08.2022 o 14:09, kekronbekron pisze: IMHO JES will not allow any job without RACF userid. It's not a matter of opinion.. Haven't you seen jobs or ad-hoc STCs show up with a 'Owner' of ? I don't know entirely, maybe +++ is defined as an ID by default in some/all ESMs.

Re: Activating healthchecker

Brian W wrote >There are some valid reasons to deactivate "some" >of the heath checks Most (perhaps not enough) checks know when to consider themselves "not applicable" in appropriate circumstances so don't need to be deactivated. Many (perhaps not enough) checks give you the flexibility (by

Re: Is JES2 z22 mode required on z/OS 2.5?

Silly question: WHAT IS THE PROBLEM? What is the problem with migration to z22 mode? Yes, the migration is mandatory, so if some obstacles exist (do they???), then it is good time to remove them. -- Radoslaw Skorupka Lodz, Poland W dniu 19.08.2022 o 01:04, IBM user pisze: Hi Mark,

Re: MCDS CDS BACKVOL fails

Second line tells you what it is. Functions within HSM (including backup) are held. - KB --- Original Message --- On Sunday, August 21st, 2022 at 12:15 PM, Jake Anderson wrote: > Hello All, > > Good morning > > I tried running HSEND BACKVOL CDS but I got failed with below message,

MCDS CDS BACKVOL fails

Hello All, Good morning I tried running HSEND BACKVOL CDS but I got failed with below message, infact I tried allocating the dataset with LLQ V0 but still it fails ARC0744E MCDS COULD NOT BE BACKED UP, RC=0036, REAS=. MIGRATION, BACKUP ARC0744E (CONT.) FRBACKUP, DUMP, AND RECYCLE HELD.