Re: Documentation RCF entry and tracking proposal on idea portal - please read and vote

Thank you for that link Ann, but I quote from the page you sent: "You will not receive a direct response to your feedback." Why not? Wouldn't a mechanism to engage in dialog about the documentation error(s)/omission(s) be far more customer-friendly and responsive to customer perceptions?

Re: Documentation RCF entry and tracking proposal on idea portal - please read and vote

Hello Peter, For information on how to leave feedback for IBM product documentation, visit: https://www.ibm.com/docs/en/about?topic=how-provide-feedback. Thank you, Ann DePaolo -- For IBM-MAIN subscribe / signoff / archive

Re: ISPF HILITE Question

On Thu, 18 May 2023 at 20:20, Steve Thompson wrote: > Or have I stumbled on a situation where ISPF and COBOL 6.x are > not in synch? > This used to be the "normal" situation for PL/I, and with PL/I builtins multiplying like rabbits, it may well be the case again. Ditto for COBOL... Robert --

ISPF HILITE Question

I have been chasing through a few IBM ISPF manuals and I am trying to figure out why, when HILITE is COBOL, certain words are "pink". Now I thought this was used to show a logic error, such as an "IF" with a missing "END-IF", or an extraneous "END-IF". Where my curiosity/confusion is, is

Re: Typo in "Summary of changes"?

Paul Gilmartin wrote, in part: >But I notice that in both XEDIT and Vim, Undo can >leave a spurious memorandum of a change. XEDIT has Undo? Since when? (No, it doesn't.) Did you mean the business where hitting ERASE EOF at the start of a line marks the MDT so XEDIT thinks the line has been

Re: VBS file read in windows - end of record issue

On Thu, 18 May 2023 11:37:18 -0500, Kirk Wolf wrote: > >To answer your other question (preserving SDW): if you copy a RECFM=VBS >dataset using DCB=RECFM=U, you will get BDWs and SDWs. > Yes. I did that with REXX in an era when REXX supported nether VBS nor U. I first used a utility (REPRO,

Re: VBS file read in windows - end of record issue

I apologize if this has already been covered on this thread, but using LF/CRLF etc on a VBS file will result in problems with binary records since they could easily contain a line terminator. To answer your other question (preserving SDW): if you copy a RECFM=VBS dataset using DCB=RECFM=U,

Re: VBS file read in windows - end of record issue

Long time ago IFASMFDP had a default BLKSIZE of 4096, but today uses SDB to match to device characteristics. However, LRECL is set to 32767 and SMF did write records that long. At last check, still did use DCBE, so features like LBI could not be used for it's output files. Note that if

Re: VBS file read in windows - end of record issue

See the references on XLRI. This should be a good start - Processing Records Longer than 32 760 Bytes - IBM Documentation This also might help -

Re: VBS file read in windows - end of record issue

Radoslaw, If you specify the LRECL and/or BLKSIZE in your program, then you can set a value that appears to flout the JCL rules. For example it used to be that IFASMFDP wrote data sets with a BLKSIZE of 32767. I am unsure if it still does. Lennie Dymoke-Bradshaw https://rsclweb.com ‘Dance

Re: z/OSMF log size

Classification: Confidential Glad to be of help -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, May 18, 2023 7:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OSMF log size [CAUTION: This Email is from outside the Organization. Unless

Re: Announcement Letters

Reminds me of someone's email signature from a long time ago which went something like: "No trees were cut down in sending this message but a large number of electrons were seriously inconvenienced." mkk On Wed, 17 May 2023 19:00:10 -0400, Bob Bridges wrote: >Wait, "improve life on the

Re: z/OSMF log size

Thanks I removed that, restarted IZUSVR1, and it seems to work. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: יום ה 18 מאי 2023 15:18 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OSMF log size Classification: Confidential YUP!

Re: z/OSMF log size

Classification: Confidential YUP! -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, May 18, 2023 7:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OSMF log size [CAUTION: This Email is from outside the Organization. Unless you trust the

Re: z/OSMF log size

I found JVM_OPTIONS=-Djavax.net.debug=all in /global/zosmf/configuration/active_configuration.cfg and in /global/zosmf/configuration/local_override.cfg Could this be causing the excessive logging? Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller

Re: z/OSMF log size

Hi, It says TRACE-N The first STDOUT in the output also says TRACE-N There are no TRACE or DEBUG options set in IZUPRM00. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jousma, David Sent: יום ה 18 מאי 2023 15:04 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:

Re: z/OSMF log size

TRACE=Y in the STC JCL? Dave Jousma From: IBM Mainframe Discussion List on behalf of Gadi Ben-Avi Date: Thursday, May 18, 2023 at 2:54 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OSMF log size Thanks, But it looks like z/OSMF is writing to much information for normal operations. I'm

Re: z/OSMF log size

Classification: Confidential 1) try Sthe SPIN (JCL?) parameter. Possibly w/Free=close on the DD statement. 2) check the log or debug levels in IZUPRMxx. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, May 18, 2023 1:01 AM To:

Re: Announcement Letters

W dniu 18.05.2023 o 01:00, Bob Bridges pisze: Wait, "improve life on the planet"? Does someone argue that email harms the planet in some way? That's a new one on me. Well, it is quite old. People calculated carbon print (energy consumed) per each mail. Of course approx. 2/3 of emails is

Re: VBS file read in windows - end of record issue

Well, can you show me a JCL job to allocate such dataset? My experience say that any attempt to create PS dataset with LRECL > ~32kB ends with JCL error and IEF638I JCL Reference clearly say that for non-VSAM dataset the maximum is 32760. For VSAM it is 32761. "Additional Syntax" says it is

Re: z/OSMF log size

Thanks, But it looks like z/OSMF is writing to much information for normal operations. I'm looking for some kind of setting to fix it. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of kekronbekron Sent: יום ה 18 מאי 2023 09:42 To: IBM-MAIN@LISTSERV.UA.EDU

Re: z/OSMF log size

Sorry, I don't know the exact name for it, but there's some timed cut-off capability that can be used to archive or make cuts in some intervals. Then, let them get actually archived into some archival product or datasets. - KB --- Original Message --- On Thursday, May 18th, 2023 at

z/OSMF log size

Hi, The size of the STDOUT output in our z/OSMF started task IZUSVR1 is over 13 million lines. Can anyone suggest how to make it a bit smaller? We are running under z/OS v2.3. Thanks Gadi -- For IBM-MAIN subscribe / signoff