Re: When did CMS stop requiring S/370 mode?

doesn't list an option on the FORMAT command to select a new format file system. Are the VM/370, VM/SE, VM/BSE, VM/SP, VM/XA (MA, SF and SP)

Re: Flashcopy for Non-SMS volume backup?

Glenn, Thank you for your excellent suggestions. We implemented things exactly your way and we're quite pleased. My POC did not use incremental flashcopy. We're using it now, based upon your suggestion, and the result is the controller does a lot less work -- which is great. The only

Re: Storage Zoning clarification

Yes it does. From the HCD manual, there's a section that talks about them Defining a special FBA device (FBA) You can use a new type of disk devices, known as Fixed Block Architecture (FBA) or Fixed Block (FB) devices. Devices of this type may be considered as a data bridge between z/OS

Re: When did CMS stop requiring S/370 mode?

On Mon, 10 May 2021 22:35:50 -0500, Alan Altmark wrote: (snippage) > >z/VM 3.1 was the last release to support 370 mode virtual machines, including >CMS. z/VM V4 (all releases) tolerated virtual machines defined with MACHINE >370, but would not instantiate them. (This was done in case of

Re: COBOL Translator name ("TNAME") ECBL, CBL370, etc

For BMC Compuware File-AID/MVS the abbreviations come from an internal table that corresponds with compiler Product code. They are not documented externally. -- For IBM-MAIN subscribe / signoff / archive access instructions,

Re: SMPE Receive Order post May 1st

On 5/10/2021 4:57 PM, Michael Babcock wrote: I did some testing on our sandbox (I commented out all ciphers except the one I was interested in and refreshed policy agent) and here’s what I found. The ECDHE ciphers were rejected but the TLS_RSA_WITH_AES_256_CBC_SHA did work (I didn’t try the

Re: COBOL Translator name ("TNAME") ECBL, CBL370, etc

Assembler (F) is IEU, not IEV.Alas, the author is no longer with us. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe Monk [joemon...@gmail.com] Sent: Wednesday, May

Re: COBOL Translator name ("TNAME") ECBL, CBL370, etc

?? 360S-AS-036 S/360 OS ASSEMBLER (E) 360S-AS-037 S/360 OS ASSEMBLER (F) 360SAS037 IEU 5734-AS1 OS ASSEMBLER H 5734AS100 IEV 5752-SC103 OS/VS ASSEMBLER (XF)5741SC103 IFO,IFN 5668-962 ASSEMBLER H V2

Re: SMPE Receive Order post May 1st

>This was confirmed by an individual that supports the server. The >ciphers mentioned on the IBM Support page are a subset of the ciphers >actually enabled. >https://www.ibm.com/support/pages/node/6417233 >I hope this helps. Is anyone still having trouble connecting? >Kurt Quackenbush --

Re: COBOL Translator name ("TNAME") ECBL, CBL370, etc

I am not familiar with codes such as ECBL or CBL370. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joe Monk Sent: Wednesday, May 12, 2021 9:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL Translator name ("TNAME")

Re: COBOL Translator name ("TNAME") ECBL, CBL370, etc

Thanks, everyone, for the quick responses. I got the answer I needed. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Gotchas with CBDQDISP / HCM?

Hi folks, I am playing a bit with CBDQDISP and trying to get it to run with HCM for z/OS. I tried using the SYS1.PROCLIB(CBDQDISP) and SYS1.SAMPLIB(CBDQDISJ), the latter while adding SYS1.SAMPLIB to APF (lab system, so no harm done security wise). The issue I am having is that when connecting

Re: COBOL Translator name ("TNAME") ECBL, CBL370, etc

Sorry, I was matching against the wring line. They say that the eyes are the third thing to go. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe Monk

Re: How companies are moving on from Cobol?

And no one explains the cost of still needing to run about 20% of your workload on a mainframe after the easy 80% has been replatformed. Mainframe pricing is all about scale. After that, the customer gets frustrated and no longer has the skills in house so they wind up spending more to let

Re: COBOL Translator name ("TNAME") ECBL, CBL370, etc

Like this? http://gsf-soft.com/Documents/PRODCODES.html Joe On Wed, May 12, 2021 at 10:40 AM Roland Kinsman wrote: > The COBOL compiler puts information in the object code identifying the > compiler with an abbreviation, for example, ECBL for Enterprise COBOL, > CBL370 indicates COBOL for MVS

COBOL Translator name ("TNAME") ECBL, CBL370, etc

The COBOL compiler puts information in the object code identifying the compiler with an abbreviation, for example, ECBL for Enterprise COBOL, CBL370 indicates COBOL for MVS & VM, etc. In the CSECT map, this is the "Translator Name." You can see it with utilities such as AMASPZAP and

Re: SMPE: Element Contains CLIST with ALIAS

On Mon, 10 May 2021 13:00:31 -0500, Paul Gilmartin wrote: > >The Ref. ...: >... >"message control statment" (dozens of times)? "MCS (Modification Control >Statement)"? >Whatever. > RCF submitted and promptly accepted for next refresh. -- gil

Re: STIMERM LT value

> Where a shop with STP and no clock drift might see this in their CLOCKxx > member: > > TIMEZONE W.08.00.00 > > ours would say (for example): > > TIMEZONE W.07.58.12 > > and this would be adjusted roughly every month to keep us within a > second or two of the real time shown on every Windows

Re: z/OS Conda install questions

Hi Lionel, I am watching your efforts closely both here and on Rocket's site. I asked the same question on the Rocket site month's ago, but you have had better response activity. My activities are on hold, until we get a Service Contract with Rocket. If that happens then I will be back into

Re: SMPE Receive Order post May 1st

Kurt, Unless I'm doing something wrong, my testing does not bear that out. The only cipher in the list was:     # Allow only AES ciphers V3CipherSuites TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 PAGENT was refreshed.  Here’s the DEBUG ALL output. SC0588 initConnection: Calling getaddrinfo()

Re: z/OS Conda install questions

Bruce, Your environment is not dissimilar to our setup at Rocket. We create a read only file system for ported tools which is shared across LPARs and Sysplexes. We don't update ported tools that frequently but when we do there is the usual backout plan you would expect from a mainframe shop.