Hello Tony, Parwez, Alan,
Thank you very much for your advice, it'a very helpful. I'm reviewing your
comments.
I understand that the number of Ethernet ports is different for each OSA
PCHPID.
The z10 BC is a our partner's machine. I checking of OSA-Express features.
We will continue to work
Hi Larry,
it might sound strange, but setting userid and password is optional, so you can
set it in the IMSConnectionSpec even though it is absent in the docs.
Denis.
-Original Message-
From: Larry Zhang <03b304d39e8e-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent:
>From a programming standpoint which is (a) more efficient, and (b) easier to
understand - Interpret or Value.
Examples:
/* rexx */
/* setup our defaults to start with */
istr = 'abc'
vstr = istr
1. IMHO, VALUE is much easier to read
2. It is trivial to use INTERPRET to assign a lower case values.
3. I'm confident that VALUE is less expensive, but it's easy to test.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Di
Is there a new edition of the Z PoOps for the Z16 (Telum)?
--
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
Is the feed to bit.listserv.ibm-main down. I have seen nothing from
it for days now.
Clark Morris
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO I
IBM-MAIN last posted 4 minutes ago.
On Mon, Sep 13, 2021 at 8:17 AM Clark Morris
<03b2c618bdfc-dmarc-requ...@listserv.ua.edu> wrote:
>
> Is the feed to bit.listserv.ibm-main down. I have seen nothing from
> it for days now.
>
> Clark Morris
>
>
On 9/13/2021 6:16 AM, Seymour J Metz wrote:
Is there a new edition of the Z PoOps for the Z16 (Telum)?
IBM *never* makes PoOp for a new machine available prior to the formal
product announcement.
Based on past behaviors and timelines, I would expect this in the
February-April 2022 time-fram
A few years back I switched from INTERPRET to VALUE due to concerns I had from
a security perspective.
Value only performs an evaluation and assigns it to a variable. Interpret lets
you do any thing.
Say for example in your sample code. If I could hijack you code and adding a
single line
Why hijack? Right your own code. Anyway, it runs under your user…
We switched some of interpret commands to value since the sending field was
larger than 256 bytes. Value don’t care.
ITschak
בתאריך יום ב׳, 13 בספט׳ 2021 ב-16:35 מאת Gary Freestone :
> A few years back I switched from INTERPRET
My main use case for interpret is passing back a string with stem variable
assignments from a procedure. Then the caller of the procedure interprets
the string - which has semicolons to separate the assignment statements.
I don't much like it but it seems the best I can do.
Martin Packer
WW z/
I use INTERPRET here and there, but pretty rarely. About the only program with
it that I use all the time is something I call "EV" (for "evaluate), that acts
as a sort of ad-hoc calculator:
parse arg v1
interpret 'v2='v1
say v1'='v2
Thus I can say on any ISPF command line "tso ev 228/15"
For stem assignments in a subroutine I prefer to use the STEMPUSH / STEMPULL
routines available from CBT. I forget the CBT file number, but you can look it
up there.
Of course a vendor can't count on those CBT routines being available at a
customer site, but for in-company solutions they work
On Mon, 13 Sep 2021 06:44:44 -0500, Lionel B. Dyck wrote:
>From a programming standpoint which is (a) more efficient, and (b) easier to
>understand - Interpret or Value.
>
>Examples:
>
>/* rexx */
>/* setup our defaults to start with */
>istr = 'abc'
>vstr = istr
>
>/* value examples */
>newvar =
On Mon, 13 Sep 2021 10:18:45 -0400, Bob Bridges wrote:
>
>But I keep thinking about the possibilities for malice in any tool I write for
>public use, and worry about it. I can't think of any examples, because as
>Itschak points out below, it's always going to run under the perpetrator's own
>ID
FWIW I attach what happens with REXX's INTERPRET vs CLIST's &&... (but
from memory, as I've had no access to a mainframe for 8+ years)
AFAIK, REXX's INTERPRET can handle only up to 3 or 4 levels of nesting -
as in INTERPRET (INTERPRET (INTERPRET etc.)) or similar - whereas CLIST
can retrieve the
On Mon, 13 Sep 2021 21:48:11 +0100, CM Poncelet wrote:
> ...
>Yes, IIRC INTERPRET returns everything in uppercase
>
It definitely does not. If you were able to try:
interpret 'X = ''Mixed Case'''
say X
you would see:
Mixed Case
> ... - whereas CLIST's "CONTROL CAPS ASIS" leaves
I meant IIRC INTERPRET returns the lowercase values of variables in
uppercase.
AFAIK "ALLOCATE DD(SYSIN) DSN(*)" is not in *CLIST* format - and I have
no idea what that would have to do with preserving lowercase chars.
A *CLIST* format would be something like "ALLOC FI(SYSIN)
DA('SYS1.PARMLIB(IEAAP
On Tue, 14 Sep 2021 00:04:20 +0100, CM Poncelet wrote:
>I meant IIRC INTERPRET returns the lowercase values of variables in
>uppercase.
>
Again, not so. INTERPRET returns values of variables ASIS. For example:
V = 'Value of V'
interpret 'x = V'
say X
shows:
Value of V
>AFAIK "A
>And You can't use coprocess if You are using EXCI.
>//Lasse=20
That changed a couple of years ago for COBOL! (Still true for PL/I)
https://www.ibm.com/support/pages/use-integrated-cics-translator-exci-batch-programs
Cheers,
TomR >> COBOL is the Language of the Future! <<
---
hi Denis, I eventually worked around this issue by starting a new project from
a very simple project setup and add my code increasingly. I doubted about our
issue was with the project set up where two versions of IMSICO jars existed and
this caused the class loader issue, which show stoppered o
Thanks, tried it and, yes
//Lasse
-Ursprungligt meddelande-
Från: IBM Mainframe Discussion List För Tom Ross
Skickat: den 14 september 2021 02:13
Till: IBM-MAIN@LISTSERV.UA.EDU
Ämne: Sv: COBOL compiler option to list libraries from which COPY members were
loaded?
>And You can't use
22 matches
Mail list logo