Re: printlog...

There are many "logs" in z/OS. And many ways to print stuff. More detail is needed to make a useful answer to this question > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CarlosM > Sent: Thursday, February 10, 2022 9:40 PM > To: IBM-MAIN@LISTSERV.UA.EDU >

Re: CICS/TS 4.1 3270 question

A possibility is that the "some terminals" are in a state affected by a prior CICS transaction. Most likely if you are using partition support and setting the presentation space incorrectly. For some terminal types CICS will not reset terminal state between transactions and inheriting unexpected

printlog...

    Is there a PRINTLOG utility for Z/OS Does anyone have an example? Thank you. Carlos Martinez SUNY DOWNSTATE -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with

FW: FYI Securing open-source software won't come cheap • The Register

https://www.theregister.com/2022/02/09/secure_open_source_software/ ​Regards, Mark Regan, K8MTR General, EN80tg CTO1 USNR-Retired (1969-1991) Nationwide Insurance, Retired, 1986-2017 z/OS Network Software Consultant (z NetView, z/OS Communications Server) Contractor, Checks & Balances, Inc.

Next z/OSMF Guild Session - Security Configuration Assistant

Join our upcoming z/OSMF Guild session featuring a deep dive on the new Security Configuration Assistant function and how to automate it using Red Hat Ansible. Regardless of your External Security Manager, Security Configuration Assistant ensures optimal performance across the security

Re: Rocket Vim fileencoding (was: ... ASCII ...)

Remember that even paranoids have real enemies. If you're forced to run in an environment with only minimal tools, it helps if you either know how to use them or at least know that they are there and where the documentation is. Would I ever use ed by choice? No. Would I sneer at someone who

Re: CICS/TS 4.1 3270 question

John, in the past I saw something similar. That time it was a "magic binary string" application sent to the terminal. It was a kind of "dirty character" into a DB. Hope this helps. Max. Il giorno gio 10 feb 2022 alle ore 15:57 John McKown < john.archie.mck...@gmail.com> ha scritto: > According

Re: [EXTERNAL] Re: Logger

Also, you can define a SMF logstream for all LPAR in a SYSPlex. So, you don't have to combine SMF offload datasets from each LPARs. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Carmen Vitullo Sent: Thursday, February 10, 2022 3:27 PM To: IBM-MAIN@LISTSERV.UA.EDU

Re: [EXTERNAL] Re: Logger

JIm's correct, default is defined and is a must, then we defined the COMPLETE logstream for each LPAR, I'm still poking around on my system, It does not look like you have to define the in memory logstreams Carmen On Thu, 10 Feb 2022 20:04:15 +, Horne, Jim wrote: >They aren't

Re: Logger

your welcome Steve, glad I could help Carmen On Thu, 10 Feb 2022 14:10:54 -0600, Steve Beaver wrote: >Damn Carmen - You hit the nail on the head > >Thank you for answering my questions > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On

Re: Logger

Damn Carmen - You hit the nail on the head Thank you for answering my questions -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, February 10, 2022 2:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Logger

Re: Logger

I'm not that knowledgeable with parsing into PERF, SEC.. if you mean you can separate the LS into different log streams, yes you can by record type, that's how my team mate did it. using LSNAME(IFASMF.COMPLETE.,TYPE(0:255)) and using an inmemory logstream

Re: [EXTERNAL] Re: Logger

They aren't "sub-logstreams," they are separate logstreams. The only SMF logstream you must have is DEFAULT, all others are optional. Jim Horne NOTICE: All information in and attached to the e-mails below may be proprietary, confidential, privileged and

Re: Logger

One thing I find interesting as I'm going through the REDBOOK, is that IN THE SMFPRMxx you can have the system Parse apart the LOGGER stream in to PERF, SEC, etc without passing the LOGSTREAMS the IFASMFPL. So it begs the question how are those sub-LOGSTREAMS handled? -Original

Re: Logger

I defined the logstream on my PLEX, and one of my teammates changed the SMF parms, we're using the IEFU29L SMF exit to dump the logstream and the dump program to dump the logstream, if you need some examples, let me know Carmen On Thu, 10 Feb 2022 13:47:55 -0600, Steve Beaver wrote: >More

Re: Logger

More interested in converting from SMF to LOGGER, having multiple LOGGER DS's like we do in SMF -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, February 10, 2022 1:42 PM To: IBM-MAIN@LISTSERV.UA.EDU

test

Testing - please ignore Pete Woo Email: p...@unum.com Office: 803.731.5868 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO

Re: Logger

On Thu, 10 Feb 2022 13:30:25 -0600, Steve Beaver wrote: dasd only Logstreams? SMF , operlog, CICS journals? Carmen >Does anyone on this list have any experience converting to logger? > > >-- >For IBM-MAIN subscribe /

Logger

Does anyone on this list have any experience converting to logger? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Test

-- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Rocket Vim fileencoding (was: ... ASCII ...)

On Thu, 10 Feb 2022 15:35:38 +, Seymour J Metz wrote: >Indeed, vim is common, but it is vi that is ubiquitous. I've used gvim, but >never vi; however, but consider it important to know about vi because it is >likely to be available on any *ix system. > A venerable expert counseled me, "Be

Re: Rocket Vim fileencoding (was: ... ASCII ...)

Indeed, vim is common, but it is vi that is ubiquitous. I've used gvim, but never vi; however, but consider it important to know about vi because it is likely to be available on any *ix system. From: IBM Mainframe Discussion List on behalf of David

CICS/TS 4.1 3270 question

According to a programmer, relaying a user error, we are "all of a sudden" getting an INVMPSZ error on _some_ terminals, but not others, when displaying a mod5 screen using BMS SEND MAP. None of the SENDs use the ALTERNATE option. All the terminals are dynamically installed using the same model,

Re: Rocket Vim fileencoding (was: ... ASCII ...)

On 10/2/22 10:38 pm, Seymour J Metz wrote: I take it you don't know the difference between vi and vim. Well, actually I do. And on most of the systems I work on vi is vim. For example, on Linux: ❯ vi --version VIM - Vi IMproved 8.1 (2018 May 18, compiled Nov 08 2021 14:21:34) On z/OS I set

Re: Rocket Vim fileencoding (was: ... ASCII ...)

My editor of choice, on Linux, is GNU Nano. https://en.wikipedia.org/wiki/GNU_nano Regards, Mark Regan, K8MTR General, EN80tg CTO1 USNR-Retired (1969-1991) Nationwide Insurance, Retired, 1986-2017 z/OS Network Software Consultant (z NetView, z/OS Communications Server) Contractor, Checks &

Re: Rocket Vim fileencoding (was: ... ASCII ...)

I take it you don't know the difference between vi and vim. From: IBM Mainframe Discussion List on behalf of David Crayford Sent: Thursday, February 10, 2022 9:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rocket Vim fileencoding (was: ... ASCII ...)

Re: Rocket Vim fileencoding (was: ... ASCII ...)

"David Crayford" wrote: > On 10/2/22 8:29 pm, Seymour J Metz wrote: > > I couldn't imagine voluntarily using an editor that didn't have a > > good macro language. The ubiquity of vi is certainly a good reason > > to learn it, but not to use it routinely. > > Huh? I use nvim (neovim) which has

Re: Rocket Vim fileencoding (was: ... ASCII ...)

On 10/2/22 8:29 pm, Seymour J Metz wrote: I couldn't imagine voluntarily using an editor that didn't have a good macro language. The ubiquity of vi is certainly a good reason to learn it, but not to use it routinely. Huh? I use nvim (neovim) which has the full force of Lua for writing

Re: Rocket Vim fileencoding (was: ... ASCII ...)

Yes, water is wet, but your claim that *some* water is wet was misleading, and could be read as claiming that not all water is wer: "The important part of USASCII is a subset of UTF-8". -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From:

Re: Rocket Vim fileencoding (was: ... ASCII ...)

On Thu, 10 Feb 2022 12:24:01 +, Seymour J Metz wrote: >ASCII is a subset of Unicode, and UTF-8 preserves all octets from 0 to 127, >including the control characters. > Water is wet. > >From: Paul Gilmartin >Sent: Wednesday, February 9, 2022 9:55 PM >

Did CP-40 support minidisks?

Was CP-67 the first OS to support carving up a real disk into minidisks, or did CP-40 already have that functionality? Does anybody have references for CP-40? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 -- For

Re: Rocket Vim fileencoding (was: ... ASCII ...)

I couldn't imagine voluntarily using an editor that didn't have a good macro language. The ubiquity of vi is certainly a good reason to learn it, but not to use it routinely. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe

Re: Rocket Vim fileencoding (was: ... ASCII ...)

ASCII is a subset of Unicode, and UTF-8 preserves all octets from 0 to 127, including the control characters. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul