I believe that you're thinking of the WorkStation Agent, which, alas, IBM has
dropped. I found it extremely useful, despite the awful limitations of
cut-and-paste.
What I really want is X11 support in TSO and ISPF.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
_
(Subject: changed again. Lotsa trimming for relevance.)
On Mon, 10 Jul 2023 09:15:00 +, Seymour J Metz wrote:
>I believe that you're thinking of the WorkStation Agent, which, alas, IBM has
>dropped. I found it extremely useful, despite the awful limitations of
>cut-and-paste.
>
>What I re
Yes, it would be easy to define structured fields for Unicode text. I would
hope that any such extension would include bidi support and the selection of
the proper first/middle/last forms in Semitic alphabets.
I'd still like to see X11 support.
From: IBM
On Mon, 10 Jul 2023 09:15:00 +, Seymour J Metz wrote:
>
>What I really want is X11 support in TSO and ISPF.
>
Does either TSO or ISPF.prohibit X11? I would imagine that an X11 client
invoked by CALL, BPXBATCN, BPXWUNIX, or SYSCALL spawn would just
work.
Subject to port availability. A forwar
I was thinking of something more ambitious; TCAS, VTIOC and ISPF support for
X11, allowing a user to log on from an X11 server.
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Monday,
Hi
Found the error.
The error was not the codepage of the setup.py, but the codepage of the
imported file _common .
Once it got chtag -tc 1047 _common.py I got further.
Thanks for the input.
BR
Frank Allan Rasmussen
--
For IB
The JCL Ref. calls "#", "$" and "@" "National" characters and 12 others
"Special" characters.
The ISPF User's Guide calls "#", "$" and "@" "Special" characters; otherwise
discussing national language support.
For clarity in discourse, shouldn't a single corporation be consistent in its
terminol
I'd choose ISPF since JCL predates ISPF by a decade or two.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
--- Original Message ---
On Monday, July 10th, 2023 at 9:27 AM, Pau
Both, cross referenced.
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Monday, July 10, 2023 12:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: "National" characters
The JCL Ref. calls "
On Mon, 10 Jul 2023 11:27:04 -0500, Paul Gilmartin wrote:
>The ISPF User's Guide calls "#", "$" and "@" "Special" characters; otherwise
>discussing national language support.
Where, specifically? In a quick search on "special character national
language" in both Vol I and Vol II, I spotted only
I am running the Db2 install / migration clist DSNTINST and am getting an
IRX0041I error:
446 +++ IRLMREG = (104857600 + (NUMTHRDS * IRLMLKUS * IRLMLKSZ))/ 1048576
IRX0041I Error running DSNTCALC, line 446: Bad arithmetic conversion
SET &OPNPTS = * ((2000 * 11)/100)
It’s difficult to use modern tools when the systems you work on are air gapped.
I can’t recreate your problem but I used a different method. I downloaded a zip
file from Github, uploaded it to z/OS and followed these steps:
jar xf psutill-master.zip
cd psutil-master
chtag -R -tc iso8859-1 .
pyt
Bill,
Did you run the DSNTEJxZ job from SDSNSAMP. This captures your existing
parameter values for use later in the installation process.
Which version of DB2 are you migrating?
Check this chapter:
https://www.ibm.com/docs/en/db2-for-zos/12?topic=jobs-running-clist-in-interactive-mode
On Tue,
Hi David,
A quick question -
Will the same chtag command work for, say, Java packages/projects?
Or, would I have to use chtag -R -tc UTF-8 if a project expects to things to be
in UTF8?
- KB
--- Original Message ---
On Tuesday, July 11th, 2023 at 3:34 AM, David Crayford
wrote:
> It
14 matches
Mail list logo
