Re: LISTDSI - hardcoded dsn vs. read in from file

Quoted strings always gave me grief. I started to use Q='7D'X and concatenate my strings this way: Str = Q||DsNAme||Q. LISTDSI(Str) PROF NOPREFIX works but can leave you that setting when you don't want it on termination. On Sat, Jan 6, 2024 at 8:00 AM Willy Jensen wrote: > > . . > >Unquote:

Re: OpenSSH CVE-2023-48795 vulnerability

You could grab the latest (unsupported) release from this repo, once it's published. Here's a link to the pull request, which introduces the latest version. The build has succeeded. https://github.com/ZOSOpenTools/opensshport/pull/6 On Saturday, January 6th, 2024 at 05:26, Filip Palian

Re: OpenSSH CVE-2023-48795 vulnerability

For this type of verification SBOMs seems to be the way moving forward: https://cyclonedx.org/use-cases/#known-vulnerabilities Cheers, FP W dniu piątek, 5 stycznia 2024 rpinion865 < 042a019916dd-dmarc-requ...@listserv.ua.edu> napisał(a): > Does anyone know if the z/OS implementation of ssh

Re: ISPF setup macro

"INRTDDN, which is valid for INFO but not for ALLOC" For alloc you must use the RTDSN(varname) parameter. But a good point, it really should have been the same. -- For IBM-MAIN subscribe / signoff / archive access instructions,

Re: LISTDSI - hardcoded dsn vs. read in from file

> . . >Unquote: return strip(space(translate(arg(1)," ","'"))) > >Isn't that a verbose equivalent of: >return strip( arg( 1 ), 'Both', ) Not exactly, the Unquote also removes spaces between the quote and the text. It has

Re: allowed characters in member name

Sounds like something NETVIEW might do. I also forgot to mention it does STOW, and so with that interface you can ignore the member name rules of JCL. Steve Thompson On 1/5/2024 3:40 PM, Nash, Jonathan S. wrote: We have a PDSE with member names starting with a left paren which were created

Re: allowed characters in member name

We have a PDSE with member names starting with a left paren which were created with some old software. I am unable to create such members in ISPF edit or to copy them with IEBCOPY. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lennie Dymoke-Bradshaw Sent:

Re: allowed characters in member name

Along those lines, does NETVIEW still use "hex" values in member names? I wondered how that would work if it (NETVIEW) was pointed to a PDSE. If I remember correctly it was using SVC 99 for some of this. Steve Thompson On 1/5/2024 3:08 PM, Seymour J Metz wrote: What about JES2 member names

Re: allowed characters in member name

What about JES2 member names starting with $? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Steve Beaver

Re: allowed characters in member name

The last time I saw PDS Member names that were not A-Z 0-9 was in Endevor. Those were/are the prior Member name backup until the package was committed Steve -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent:

Re: allowed characters in member name

On Fri, 5 Jan 2024 18:33:40 +, Sri h Kolusu wrote: >>> What characters are allowed in JCL when specifying member name? > >Radoslaw, >In general, PDS member naming rules are ( assuming code page 037) > >• A member name cannot be longer than eight characters. >• The first member

Zero Trust Architecture

Has anyone in the group started Zero Trust Architecture? If so, what have you done Steve -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the

Re: allowed characters in member name

>> What characters are allowed in JCL when specifying member name? Radoslaw, In general, PDS member naming rules are ( assuming code page 037) • A member name cannot be longer than eight characters. • The first member character must be either a letter or one of the following three

Re: allowed characters in member name

Radoslaw, >From memory, this is simply the ALPHANUMNAT set. Alphabetic chars (upper >case), Numerics and the national chars (#$@). First char may not be numeric. Lennie -Original Message- From: IBM Mainframe Discussion List On Behalf Of Radoslaw Skorupka Sent: 05 January 2024 17:18 To:

Re: ISPF setup macro

I've been using BPXWDYN for allocation and concatenation, but I had a problem with an error code -24. The fourth keyword was SHR, which left me scratching my head. It turns out that the *3RD* key was INRTDDN, which is valid for INFO but not for ALLOC; once I corrected that, things were better.

Re: SMP/E JCLIN processing for job updates

FYI again.. perhaps a little closer Vickie Dault Spahn eMail:  vickie_da...@triserv.com Cell    (916) 792-7720 Alternate Cellphone (916) 792-7850 Web:  www.triserv.com    -Original Message- From: IBM Mainframe Discussion List On Behalf Of Bill Giannelli Sent: Friday, April

Re: ISPF setup macro

My assumption is that it uses the DYNALLOC concatenation facility. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Jon Perryman Sent:

Re: Checking status of multiple datasets in CLIST and REXX

True, but I want to distinguish between FB and VVB. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Jon Perryman Sent: Friday, December 29,

Re: IBM-MAIN access with Usenet / news (NNTP) reader

TA (albeit many, if not all, USENET servers, e.g., eternal-september.org, are filled with SPAM :( -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO

allowed characters in member name

(This is somehow Friday question, but at least on topic. :-)  ) What characters are allowed in JCL when specifying member name? I mean constructs like the following: //ANY DD DSN=HLQ.DATASET(MEMBER) Note, it is not about PDS/PDSE itself and I have seen SMPSCDS member names (as well as PDSMAN

Re: OpenSSH CVE-2023-48795 vulnerability

The IBM SECINT portal is what I searched. Sent with Proton Mail secure email. On Friday, January 5th, 2024 at 10:47 AM, Allan Staller <0387911dea17-dmarc-requ...@listserv.ua.edu> wrote: > Classification: Confidential > > IBM has a subscription only list for SECINT PTFs. This

Re: OpenSSH CVE-2023-48795 vulnerability

Classification: Confidential IBM has a subscription only list for SECINT PTFs. This information is not openly published. -Original Message- From: IBM Mainframe Discussion List On Behalf Of rpinion865 Sent: Friday, January 5, 2024 9:39 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:

Re: OpenSSH CVE-2023-48795 vulnerability

I have already searched there and did not find anything related to this particular vulnerability. I did find one PTF from 2023 which is for ssh. That PTF is applied on our sandbox LPAR, scheduled to be rolled out into production shortly. Also, the IBM documentation for z/OS 2.4 SSH states

Re: IBM-MAIN access with Usenet / news (NNTP) reader

IIRC the list is sent to USENET using a one way link and it is not possible to send posts back to the link from USENET. This has been discussed before. Search the archives for more information. -- Tom Marchant On Fri, 5 Jan 2024 04:33:02 -0600, Niemand @ thuis.nl wrote: >Is access possible

Re: OpenSSH CVE-2023-48795 vulnerability

This would be found in the IBM Security Portal. Here is information on registering to obtain access: https://www.ibm.com/community/z/wp-content/uploads/sites/14/2022/06/zSystem-Integrity.pdf Kirk Wolf Dovetailed Technologies http:// coztoolkit.com On Fri, Jan 5, 2024, at

Re: LISTDSI - hardcoded dsn vs. read in from file

On Fri, 5 Jan 2024 03:06:10 -0600, Willy Jensen wrote: >or requote as a function, I think it looks nicer > > cc=Listdsi(requote(ds)) > . . >Unquote: return

Current Mailing Address

Dear Folks,     Sam Golob's current (snail mail) mailing address has changed.     It is now:   Sam Golob,  P.O. Box 702,  Pomona, NY 10970     I am trying to change all occurrences of the old address on the CBT Tape, but it is difficult.  Therefore this notice.     Thanks.     All the best

Netview, REXX and assembler interfaces for variable access

Hi, I am trying to make a REXX function writen in assembler run in Netview REXX. The function in question reads. lists and writes variables, it uses IRXEXCOM for variable access, IRXSTK for stack access and IRXSAY for terminal output. When running in Netview it doesn't abend, but it doesn't do

OpenSSH CVE-2023-48795 vulnerability

Does anyone know if the z/OS implementation of ssh is vulnerable to CVE-2023048795? I tried searching for z/OS and OpenSSH (CVE-2023-48795). But, I did not get any hits specific to z/OS. Thanks in advance. Cross posting to IBMTCP-L and IBM Main Sent with [Proton Mail](https://proton.me/)

IBM-MAIN access with Usenet / news (NNTP) reader

Is access possible to the UA Listserv via an NNTP client, e.g., Thunderbird? And if so, what is the URI of the server? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu

Re: LISTDSI - hardcoded dsn vs. read in from file

or requote as a function, I think it looks nicer cc=Listdsi(requote(ds)) . . Unquote: return strip(space(translate(arg(1)," ","'"))) Requote: if arg(1)='' then

Re: LISTDSI - hardcoded dsn vs. read in from file

Instead of changing the TSO profile, I usually remove quotes using a function like so: cc=Listdsi("'"unquote(ds)"'") . . Unquote: return strip(space(translate(arg(1)," ","'")))

Re: Digital Certificates -- Site Certificate

IBM doc says Site certificateA certificate that is associated with an off-platform server or other network entity, such as a peer VPN server. This category of certificate can also be used to share a single certificate and its private key among multiple RACF user IDs. When used for sharing, a

Re: RACF and Encryption (Cross Posted

I wrote One minute MVS – Using individual data set encryption on z/OS which may help you get started. For example you'll need ICSF. Colin On Thu, 4 Jan 2024 at 20:36, Steve Beaver <

Re: LE C growing heap issue

Have you tried heappools? One problem with storage managers is that you get fragmentation. By using heap pools - so you get pools of say 2KB, 4KB, 16KB, 64KB etc you use a bit more space overall, but the storage can be reused better. Turn on heappools - look at the reports and it recommends new