SMS dataset oddity with COM-Plete

Hi, One of our customers is running an old(er) version of Software AG's Com-Plete (version 6.4.1) along with testing version 6.8.1, and we have found that when a dataset (any sequential or PDS) is moved from a regular 3390-3 to a 3390-3 that is part of a storage group (same raid box, and close

Re: PR/SM LPAR Controls Change Running System

In many/most?/all? of the HMC LPAR controls, you have three options: only change running system, only save changes to activation profile, or do both. The LPAR (Image) profile comes into play any time the LPAR is activated, which includes POR. Unless the profile has been updated one way or

Re: PR/SM LPAR Controls Change Running System

In my understanding both pages are correct, you lose the changes after a POR, you also lose the changes if you activate the partition. When you IPL by Activate you use the activation profile settings. You can IPL with the Load command to not re-activate the LPAR and use the previous defined

Re: Question for COBOL users

On Fri, 16 Feb 2018 11:13:05 -0800, Tom Ross wrote: > >In response to other posts and Frank, I agree that we should answer the >RFE for a change to our SYSOPTF support as: "AVAILABLE: Use PARMDD" > Yaaay! Now you may have to deal with, "But that's not the way we planned to do it." If PARMDD

Re: Question for COBOL users

>FWIW, I am guessing "255" was simply a brain-glitch for 100, and had no >basis in any actual technology. Charles, you nailed my brain fart exactly! In response to other posts and Frank, I agree that we should answer the RFE for a change to our SYSOPTF support as: "AVAILABLE: Use PARMDD"

IBM Debug tool issue

>When using Debug Tool under CICS, every time a CALL statement is encountere= >d the debugger steps into the called program. >Is there a way to just have the called program called and not show its inte= >rnal workings. > >We are using Debug Tool v14.1, z/OS v2.2, COBOL v6 and CICS TS v5.4. I

PR/SM LPAR Controls Change Running System

Hi List, I have a question about what we recently experienced when dealing with Defined Capacity changes. Say I have a production LPAR with a defined capacity of 100 and a tech-only LPAR with 10. Management decides that we can afford an extra 2 MSU, temporarily. So I enter Change LPAR

Re: Parmlib members change control?

Good lord no. I'm reminded that somehow ("magically I guess"), we all managed to survive the 60s, 70s, 80s, and even the early 90s without this formal change control nonsense. If you must track, then the product from action software works. Otherwise no, just no, easy solution below.

Re: Question: Users of Pacific Systems Group -- Vendor

Our Systems Development tested the ZWESASY Product as a “front-end” to CA-Easytrieve (we migrated away from CA Products). They were satisfied and we have been using it in Production for about three months. My only issue with it is it does not use Easytrieve Macros. Thank You, Len Sasso

Re: J line command was: TSO temp dataset

Thanks, Kolusu! That was it. I haven't thought about PACK for so long that it never crossed my mind. I thought I had PACK OFF in everything because I've seen it cause issues in the past. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On

Re: small MPF exit question concerning 'sticky' console messages

You are correct. Thanks. Tony Thigpen Vernooij, Kees (ITOPT1) - KLM wrote on 02/16/2018 08:42 AM: I think your problem is not the message but the console. I suppose this is a WTOR and that is sticky. It only remains on the console if the console is in MODE=RD, not in MODE=R. Kees.

Re: Question: Users of Pacific Systems Group -- Vendor

We trialed their other product SMF Writer. I liked the product. Unfortunately, upper management didn't want to spend the money to acquire the product. In comparison to what we recently spent on hardware upgrades, that cost was insignificant. -Original Message- From: IBM Mainframe

Question: Users of Pacific Systems Group -- Vendor

I'm looking for users of Pacific Systems Group software, in particular z-Writer and its "front-ends" for other products, specifically ZWQUIK and ZWEASY. I'd like to know how well these work for you and how Pacific Systems Group is as a vendor. Regards, Steve Thompson

Re: small MPF exit question concerning 'sticky' console messages

I think your problem is not the message but the console. I suppose this is a WTOR and that is sticky. It only remains on the console if the console is in MODE=RD, not in MODE=R. Kees. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >

small MPF exit question concerning 'sticky' console messages

The programmers have a Cobol program that uses: DISPLAY OPR-MSG UPON CONSOLE. DISPLAY 'OPERATOR ACTION: IGNORE, RETRY, CANCEL' UPON CONSOLE. MOVE SPACES TO OPR-RPL. ACCEPT OPR-RPL FROM CONSOLE. This shows up on the console as: +OPERATOR ACTION: IGNORE, RETRY, CANCEL @15 IGZI

Re: Parmlib members change control?

Thanks to all who have responded - it looks like we are going to at least try the Git solution. In all my past placements as a sysprog, 'change control' or something like it has been part of the job, along with the associated 'royal pain' as Seymour rightly describes it. In this particular

Re: TSO temp dataset

Elardus, Thanks for the correction. I had read your reply, but the thread at that stage sounded to me like zSECURE built the JCL, and then the OP manually submitted it. I see that was incorrect, and we're just rehashing your original advice. Ron -Original Message- From: IBM