Re: PC on z/VSE, ...

[Chuck]

z/VSE supports PCs via the same setup macros as z/OS but it does not support 
system wide PCs available to all tasks in the system. 

Chuck Arney

> On Jul 27, 2021, at 7:40 PM, Tony Thigpen  wrote:
> 
> BSI's IPV6/VSE also uses it (as an option).
> 
> Tony Thigpen
> 
> Steve Austin wrote on 7/27/21 9:13 AM:
>> I've used them on z/VSE as does CICS I believe. Somewhat more limited than
>> on z/OS from what I remember.
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>> Behalf Of Seymour J Metz
>> Sent: Tuesday, July 27, 2021 2:06 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: PC on z/VSE, ...
>> Does anybody know whether anything other than MVS uses the program call
>> facility?
>> --
>> Shmuel (Seymour J.) Metz
>> http://mason.gmu.edu/~smetz3
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions, send email
>> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> -- 
>> This e-mail message has been scanned and cleared by Google Message Security
>> and the UNICOM Global security systems. This message is for the named
>> person's use only. If you receive this message in error, please delete it
>> and notify the sender.
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 

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

Re: PC on z/VSE, ...

[Tony Thigpen]

BSI's IPV6/VSE also uses it (as an option).

Tony Thigpen

Steve Austin wrote on 7/27/21 9:13 AM:

I've used them on z/VSE as does CICS I believe. Somewhat more limited than
on z/OS from what I remember.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, July 27, 2021 2:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: PC on z/VSE, ...

Does anybody know whether anything other than MVS uses the program call
facility?



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

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

--
This e-mail message has been scanned and cleared by Google Message Security
and the UNICOM Global security systems. This message is for the named
person's use only. If you receive this message in error, please delete it
and notify the sender.

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



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

Re: "(watch the wrap)"

[Phil Smith III]

Charles wrote:

> I don't see an apology; I see a courtesy warning.

 

Same here. Folks with stupidly broken corporate email systems may not have the 
control they'd like.

 

When I was at Sterling, outbound email would randomly show 
@reston.vmd.sterling.com (or thereabouts) instead of @sterling.com.
Played havoc with lists and the like. Nobody ever figured it out before CA ate 
them.


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

Re: [External] Re: FTP distributed system EBCDIC encoded file

[Pommier, Rex]

Frank,

Have you tried FTPing it as binary into a Unix file instead of a dataset?  I 
would think the Unix file system would happily accept the newline delimiter.  

Rex


On Tue, 27 Jul 2021 17:01:56 -0500, Frank Swarbrick wrote:

>We have a vendor that is providing a file that is EBCDIC (IBM-1140) encoded, 
>but also includes an NL record/line terminator.  The source system is NOT a 
>mainframe system.  I'm trying to figure out how to FTP the file to the 
>mainframe and have it treat NL as, well, NL; i.e. a record terminator.  Binary 
>mode (no SITE options) doesn't work because it stores the NL characters.  
>ASCII mode (no SITE options) doesn't work, I believe because it still expects 
>the CRLF delimiter.  I tried specifying "SITE TYPE E" (EBCDIC) and that also 
>does not eliminate the NL delimiter.
>
>Any thoughts?  We're seeing if the vendor can just not use a delimiter at all, 
>but no luck yet.
> 

>Note: They can create it in UTF-8, but they are including the UTF-8 Byte Order 
>Mark (BOM).  I am able to get z/OS to strip the BOM, but I have to specify the 
>transmission as being "multi-byte", so the destination has to be VB.  Which we 
>can deal with, but we'd prefer FB as that is how we have it from the old 
>vendor.
>


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


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

Re: FTP distributed system EBCDIC encoded file

[Paul Gilmartin]

On Tue, 27 Jul 2021 17:01:56 -0500, Frank Swarbrick wrote:

>We have a vendor that is providing a file that is EBCDIC (IBM-1140) encoded, 
>but also includes an NL record/line terminator.  The source system is NOT a 
>mainframe system.  I'm trying to figure out how to FTP the file to the 
>mainframe and have it treat NL as, well, NL; i.e. a record terminator.  Binary 
>mode (no SITE options) doesn't work because it stores the NL characters.  
>ASCII mode (no SITE options) doesn't work, I believe because it still expects 
>the CRLF delimiter.  I tried specifying "SITE TYPE E" (EBCDIC) and that also 
>does not eliminate the NL delimiter.
>
>Any thoughts?  We're seeing if the vendor can just not use a delimiter at all, 
>but no luck yet.
> 
Doesn't z/OS use NL as its line separator?  Verify/refute this with:
echo 'foo
bar' | od -tx1

I'd expect you to see:
000 86 96 96 15 82 81 99 25
010

where the x'15' is the NL.  I expect transfer in binary to preserve the NL and 
simply work.

>Note: They can create it in UTF-8, but they are including the UTF-8 Byte Order 
>Mark (BOM).  I am able to get z/OS to strip the BOM, but I have to specify the 
>transmission as being "multi-byte", so the destination has to be VB.  Which we 
>can deal with, but we'd prefer FB as that is how we have it from the old 
>vendor.
>
Use of a BOM with UTF-8 is generally deprecated.

-- gil

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

Re: FTP distributed system EBCDIC encoded file

[Phil Smith III]

What Charles said. If you have Pipelines, this is trivial.

 

...phsiii


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

Re: FTP distributed system EBCDIC encoded file

[Charles Mills]

Keep the NLs and write a quick and dirty to post-process, splitting the 
records? CharlesSent from a mobile; please excuse the brevity.
 Original message From: Frank Swarbrick 
 Date: 7/27/21  6:01 PM  (GMT-05:00) To: 
IBM-MAIN@LISTSERV.UA.EDU Subject: FTP distributed system EBCDIC encoded file We 
have a vendor that is providing a file that is EBCDIC (IBM-1140) encoded, but 
also includes an NL record/line terminator.  The source system is NOT a 
mainframe system.  I'm trying to figure out how to FTP the file to the 
mainframe and have it treat NL as, well, NL; i.e. a record terminator.  Binary 
mode (no SITE options) doesn't work because it stores the NL characters.  ASCII 
mode (no SITE options) doesn't work, I believe because it still expects the 
CRLF delimiter.  I tried specifying "SITE TYPE E" (EBCDIC) and that also does 
not eliminate the NL delimiter.Any thoughts?  We're seeing if the vendor can 
just not use a delimiter at all, but no luck yet.Note: They can create it in 
UTF-8, but they are including the UTF-8 Byte Order Mark (BOM).  I am able to 
get z/OS to strip the BOM, but I have to specify the transmission as being 
"multi-byte", so the destination has to be VB.  Which we can deal with, but 
we'd prefer FB as that is how we have it from the old vendor.FYI, here are the 
3 "SITE" commands mentioned in the note 
above:encoding=mbcsmbdataconn=(ibm-1140,utf-8)UnicodeFileSystemBOM=never--For
 IBM-MAIN subscribe / signoff / archive access instructions,send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

FTP distributed system EBCDIC encoded file

[Frank Swarbrick]

We have a vendor that is providing a file that is EBCDIC (IBM-1140) encoded, 
but also includes an NL record/line terminator.  The source system is NOT a 
mainframe system.  I'm trying to figure out how to FTP the file to the 
mainframe and have it treat NL as, well, NL; i.e. a record terminator.  Binary 
mode (no SITE options) doesn't work because it stores the NL characters.  ASCII 
mode (no SITE options) doesn't work, I believe because it still expects the 
CRLF delimiter.  I tried specifying "SITE TYPE E" (EBCDIC) and that also does 
not eliminate the NL delimiter.

Any thoughts?  We're seeing if the vendor can just not use a delimiter at all, 
but no luck yet.

Note: They can create it in UTF-8, but they are including the UTF-8 Byte Order 
Mark (BOM).  I am able to get z/OS to strip the BOM, but I have to specify the 
transmission as being "multi-byte", so the destination has to be VB.  Which we 
can deal with, but we'd prefer FB as that is how we have it from the old vendor.

FYI, here are the 3 "SITE" commands mentioned in the note above:
encoding=mbcs
mbdataconn=(ibm-1140,utf-8)
UnicodeFileSystemBOM=never

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

Re: "(watch the wrap)"

[Charles Mills]

I don't see an apology; I see a courtesy warning. CharlesSent from a mobile; 
please excuse the brevity.
 Original message From: Paul Gilmartin 
<000433f07816-dmarc-requ...@listserv.ua.edu> Date: 7/27/21  5:37 PM  
(GMT-05:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: "(watch the wrap)" On Tue, 27 
Jul 2021 16:04:39 +, Rob Scott wrote:>>... (watch the wrap) 
:>https://github.com/IBM/IBM-Z-zOS/blob/main/zOS-Education/zOS-V2.5-Education/IEAV2R5%20SDSF.pdf.>>...
 (watch the wrap) 
:>https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R4sc274942/$file/isfa700_v2r4.pdf>Your
 message arrived in my Inbox with headers:    Content-Type: text/plain; 
charset=WINDOWS-1252    Content-Transfer-Encoding: quoted-printableAny 
well-featured reader can deal with this without sufferingwrapping problems.  
You shouldn't be obliged to apologizefor you recipients' deficient 
software.Alas, another recent message with a similar Subject: appeared with:    
Content-Transfer-Encoding: 7bitand URLs adversely wrapped.  That author should 
get better Mail software,or configure the existing one better.-- 
gil--For 
IBM-MAIN subscribe / signoff / archive access instructions,send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

"(watch the wrap)"

[Paul Gilmartin]

On Tue, 27 Jul 2021 16:04:39 +, Rob Scott wrote:
>
>... (watch the wrap) :
>https://github.com/IBM/IBM-Z-zOS/blob/main/zOS-Education/zOS-V2.5-Education/IEAV2R5%20SDSF.pdf.
>
>... (watch the wrap) :
>https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R4sc274942/$file/isfa700_v2r4.pdf
>
Your message arrived in my Inbox with headers:
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Any well-featured reader can deal with this without suffering
wrapping problems.  You shouldn't be obliged to apologize
for you recipients' deficient software.

Alas, another recent message with a similar Subject: appeared with:
Content-Transfer-Encoding: 7bit
and URLs adversely wrapped.  That author should get better Mail software,
or configure the existing one better.

-- gil

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

SDSF for z/OS 2.5 - Overview of changes/enhancements

[Rob Scott]

IBM have just made public a set of PDFs on GitHub that highlight various new 
things in z/OS 2.5, including the following link for SDSF (watch the wrap) :

https://github.com/IBM/IBM-Z-zOS/blob/main/zOS-Education/zOS-V2.5-Education/IEAV2R5%20SDSF.pdf

I will also be presenting "More ways to manage your z/OS with SDSF for z/OS 
2.5" at Share in August that will cover this announcement in more detail.

Hopefully there are some new things in SDSF 2.5 that you will like, but please 
take note of the SAF security requirement and plan your migration accordingly 
if you still use the old internal security definitions and/or the ISFUSER exit.

We have a new SDSF Security Migration guide manual available to help anyone 
that has still to convert to SAF (watch the wrap) :

https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R4sc274942/$file/isfa700_v2r4.pdf


Rob Scott
Principal Architect, Mainframe Systems Tools
Distinguished Engineer
Rocket Software
77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA
Tel: +1.781.684.2305
Email: rsc...@rs.com
Web: www.rocketsoftware.com



Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

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

Announcing IBM z/OS V2.5, Next-Gen Operating System Designed for Hybrid Cloud and AI

[Phil Smith III]

 

https://newsroom.ibm.com/2021-07-27-Announcing-IBM-z-OS-V2-5,-Next-Gen-Opera
ting-System-Designed-for-Hybrid-Cloud-and-AI


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

Re: PC on z/VSE, ...

[Steve Austin]

I've used them on z/VSE as does CICS I believe. Somewhat more limited than
on z/OS from what I remember.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, July 27, 2021 2:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: PC on z/VSE, ...

Does anybody know whether anything other than MVS uses the program call
facility?



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

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

-- 
This e-mail message has been scanned and cleared by Google Message Security 
and the UNICOM Global security systems. This message is for the named 
person's use only. If you receive this message in error, please delete it 
and notify the sender. 

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

PC on z/VSE, ...

[Seymour J Metz]

Does anybody know whether anything other than MVS uses the program call 
facility?



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

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

Re: Mixing C/C++ with LE-conforming IBM HLASM

[David Crayford]

On 25/07/2021 1:01 am, Kirk Wolf wrote:
We recently released two new shell command utilities in Co:Z which 
have all sorts of options for loading/unloading PDS/PDSEs to/from zFS 
files.


https://www.dovetail.com/docs/zos-utilities/dsp-ref_getpds.html
https://dovetail.com/docs/zos-utilities/dsp-ref_putpds.html

The code is 98% C++, with bpam/bsam assembler routines.   Our C++ is 
31-bit LE with XPLINK  (IMO the only rational linkage for C++ at 
scale).  Our assembler code is quite small and uses  XPLINK linkage 
macros (EDCXPRLG, EDCXEPLG) and also the XPLINK stack local data.  
This is *so* much nicer than the old way of writing reentrant code.    
All of the BSAM fancies (DECB/buffer queue, record blocking, etc) is 
done in C++.  Only one DCB (BPAM/BSAM).


The performance of loading/unloading a large PDS/PDSE is great - like 
two orders of magnitude faster than /bin/cp which opens the dataset 
for each and every member :-)
We also support ISPF-style ENQs with DISP=SHR, which is really handy 
for many use cases, like devops. 



We're using getpds/putpds for new DevOps tooling to sync files to/from 
the file system to data sets. Not only is the performance superb (cp 
taking 2 minds to move a large PDS as opposed to 3 seconds) the ability 
to write to a PDS with DISP=SHR is a game changer as we only want to 
stage using optimistic locking.


This is top notch software engineering!

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