I don’t know if it answers part of your question, but i have clients who used
to use categories for production and catégories for DR to be able to write in
their vts on specific tape ranges. And depending on the licences your vts has,
you have to consider tape allocation : imagine you want to
Sorry, I misunderstood the question.
In IBM's TS7700, you can only select MEDIA1 or MEDIA2 as they only emulate
3490 and 3490E. 18-track and 36-track.
I only use MEDIA2, with dataclas assigning either 6GB or 25GB volume sizes.
I don't know about other virtual tape systems, which may be able to
That's good answer to the question not asked.
Yes, different categories are good for multi-tenancy, even if it is set
of RMM, each having own db.
However I'm asking for the reason for having multiple categories
logically assigned to single system.
I excluded various (virtual) tape capacities
If different LPARs using the tape library have different TMCs, then they
must also have different category codes assigned so the correct tapes are
used for scratch mounts.
On Sat, 20 May 2023 at 02:43, Radoslaw Skorupka <
0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote:
> Volume
Volume categories (0001, 0002, and so on) are useful for library
partitioning. Each SMS-plex can use it's own set of categories (00x1,
00x2...).
Categorie are good to request big tape of small tape (JA, JK) or newer
or older (JB, JC...).
However the last sentence was good for real tapes.
In
On 2023-04-14 13:56 PM, Paul Gilmartin wrote:
enhances "-" character
It's amazing that they have found a way to enhance a character. ;)
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support:
On Fri, 14 Apr 2023 11:59:28 -0400, Tony Harminc wrote:
>I got a notification that New Function APAR /OA64061 has closed.
>https://www.ibm.com/support/pages/apar/OA64061
>
Thanks. OS Release? Availability date? Documentation?
>The date command enhances -d option to displays the operating
I got a notification that New Function APAR /OA64061 has closed.
https://www.ibm.com/support/pages/apar/OA64061
The description:
* USERS AFFECTED: z/OS users of the date, find, cat, ps*
* command.
Robert Prins wrote:
>https://ibmmainframes.com/viewtopic.php?t=68675
That's pretty good. I'm'a try it on a few of my younger colleagues, see if
they get it-betting they don't.
--
For IBM-MAIN subscribe / signoff / archive
https://ibmmainframes.com/viewtopic.php?t=68675
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Sunday, May 24, 2020 11:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
On Sun, 24 May 2020 18:26:13 -0700, Charles Mills wrote:
>...
>+1
On Sun, 24 May 2020 18:26:13 -0700, Charles Mills wrote:
>...
>+1 (What the H*** is gained by uppercasing a CART where the underlying
>service supports any 64-bit value? Don't over validate! This is the problem
>with various utilities that could handle UNIX files except that the utility
smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Sunday, May 24, 2020 9:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
+1 (SUBMIT)
+1 (Doc)
+1 (What
-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
On Mon, 25 May 2020 00:53:04 +, Seymour J Metz wrote:
>Never mind case; when will SUBMIT recognize that 80 is not the only integer?
>
>Also, when TSO (sub)commands upper case their input, the documentati
ts slashes or lowercase letters.)
I've done my part on various RCF's but not so far on this one.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Sunday, May 24, 2020 5:53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
On Mon, 25 May 2020 00:53:04 +, Seymour J Metz wrote:
>Never mind case; when will SUBMIT recognize that 80 is not the only integer?
>
>Also, when TSO (sub)commands upper case their input, the documentation should
>say so in an obvious location as part of the (sub)command description.
>
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Sunday, May 24, 2020 7:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO
On Sun, 24 May 2020 14:26:51 -0700, Charles Mills wrote:
>
>'MyCart01' (as written, in camel-case) was my intended CART and it is a valid
>CART: a CART may have any 64-bit value. The problem was that the CONSOLE
>command uppercased it to MYCART01. Yes, had I written my Rexx in such a way as
>to
@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Sunday, May 24, 2020 5:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
The problem was NOT that Rexx (or my coding style) failed to uppercase an
operand; the problem was that TSO did
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Seymour J Metz
Sent: Saturday, May 23, 2020 11:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
> You seem stuck on this capitalization thing.
You seem to forget t
hs.com]
Sent: Sunday, May 24, 2020 1:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Metz wrote:
>Well, I've only been using REXX for 35 years. The problems that I have seen
>from not quoting words have been few and far between, not ne
Metz wrote:
>Well, I've only been using REXX for 35 years. The problems that I have seen
>from not quoting words have been few and far between, not nearly as many as,
>e.g., problems related to continuation, omitting a period in a stem, incorrect
>capitalization in a string literal.
You
(Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Friday, May 22, 2020 8:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't
t;> ____
> >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on
> behalf
> >> of Steve Smith [sasd...@gmail.com]
> >> Sent: Friday, May 22, 2020 3:00 PM
> >> To: IBM-MAIN@LISTSERV.UA.EDU
> >> Su
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
of Steve Smith [sasd...@gmail.com]
Sent: Friday, May 22, 2020 3:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Case sensitivity is the root of all
Slight diversion. A colleague wanted some REXX code so I sent it as an XMIT
file. He was working remotely and said, the RECEIVE fails.
When I next saw him, I went to his desk and watched the RECEIVE command.
Boom, "UNABLE TO ALLOCATE LOG.MISC".
He had TSO PROFILE(NOPREFIX) and didn't have RACF
led
labels that the interpreter may miss.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Phil Smith III
Sent: Friday, May 22, 2020 5:48 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Metz wrote:
> Running with signal on novalue and quoting everything leads to hard-to-debug
> surprises errors when you get the case wrong (present
example is typical.) ;-)
After almost 40 years of writing Rexx, I've never had that problem. Quoting
literals avoids far more problems than it
-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Friday, May 22, 2020 4:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
True enough, but in my (actual) Rexx programs I always code Signal On
Novalue. To do otherwise
Metz
Sent: Friday, May 22, 2020 12:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Hence my quote: had he not quoted the value then it would have been a symbol
and REXX would have translated it to upper case
] on behalf of
Robert Garrett [rob...@garrettfamily.us]
Sent: Friday, May 22, 2020 1:45 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Your problem is caused by using lower case characters in your CART parameter
value, the value of variable MyCart. If you
a case for case dependent languages. It
> helps if you have a good IDE.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> of Steve Smit
Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Steve Smith [sasd...@gmail.com]
Sent: Friday, May 22, 2020 3:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Case sensitivity is the root of all evil.
sas
Disclaimer: The above may contain
; REXX normally translates
names to upper case.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Friday, May 22, 2020 1:53 PM
Case sensitivity is the root of all evil.
sas
Disclaimer: The above may contain excessive generalization, hyperbole, and
offend your sensibilities. I'd say I'm sorry, but that would just add
flat-out lying to the mix.
--
For
ot;TSOEXEC CONSOLE ACTIVATE NAME("con_name") CART("Cart_V")"
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of Charles Mills
> Sent: Friday, May 22, 2020 1:53 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Friday F
XEC CONSPROF SOLDISP(NO) SOLNUM(400)"
/*
activate Console services*/
"TSOEXEC CONSOLE ACTIVATE NAME("con_name") CART("Cart_V")"
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Charles Mills
Sent: Friday, May 22, 202
ot;'"||MyCart||"'" .
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Robert Garrett
Sent: Friday, May 22, 2020 10:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Y
-
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Friday, May 22, 2020 11:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
I called my congressman and he said quote
I'd like to help you son, but you're too young
SYSCMD() is a valid alternative to Address Console but either one is good, and
the Address Console in my Rexx is not the problem.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of scott Ford
Sent: Friday, May 22, 2020 9:43 AM
Nope.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Richards, Robert B.
Sent: Friday, May 22, 2020 9:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
If I turn on HILITE
i, May 22, 2020 at 12:35 PM Charles Mills wrote:
>
>> Message handling is fine, other than one very specific problem that is
>> inherent in the Rexx code posted.
>>
>> Note this is a Friday Folly, not a "real question." I know the answer
>> (after 2+ hours
Charles:
I think that should be 'address mvs' ...scott
On Fri, May 22, 2020 at 12:35 PM Charles Mills wrote:
> Message handling is fine, other than one very specific problem that is
> inherent in the Rexx code posted.
>
> Note this is a Friday Folly, not a "real question.&q
If I turn on HILITE, will the answer become apparent?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Charles Mills
Sent: Friday, May 22, 2020 12:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Message handling
Message handling is fine, other than one very specific problem that is inherent
in the Rexx code posted.
Note this is a Friday Folly, not a "real question." I know the answer (after 2+
hours of debug struggle!).
Charles
-Original Message-
From: IBM Mainframe Discu
Nope, it is fine.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Richards, Robert B.
Sent: Friday, May 22, 2020 8:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387
Address
ttp://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> of Charles Mills [charl...@mcn.org]
> Sent: Friday, May 22, 2020 10:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Friday Follies/Why
Mills [charl...@mcn.org]
Sent: Friday, May 22, 2020 10:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Friday Follies/Why won't this work?/TSO Rant #387
What is wrong with this Rexx? (I spent about two hours debugging before I
solved it.) The problem is right here on this page: the answer
Address Console in wrong location?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Charles Mills
Sent: Friday, May 22, 2020 10:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Friday Follies/Why won't this work?/TSO Rant #387
What is wrong with this Rexx? (I spent about
What is wrong with this Rexx? (I spent about two hours debugging before I
solved it.) The problem is right here on this page: the answer is NOT
something in RACF or JES2. It's not something missing: it's a sin of
commission, not a sin of omission. The below will never work. That is, the
output
conditional macro assembler as in (readable form):
.EXTRM ANOP TERMINAL EXCLUDES DEFINITION
.*
SETA 1
SETC ''
conditional macro assembler as in:
.EXTRM ANOP TERMINAL EXCLUDES DEFINITION
00075800
.*
00075900
SETA 1
00076000
SETC ''
On Wed, 29 Apr 2020 02:57:23 +0100, CM Poncelet wrote:
>... but that's the only way to do it in conditional macro assembler; so
>what me worry about 3GL's? :)
>
What hardware? Doesn't Divide leave the quotient in one register and the
remainder in an adjacent one?
>On 28/04/2020 10:46, David
... but that's the only way to do it in conditional macro assembler; so
what me worry about 3GL's? :)
On 28/04/2020 10:46, David Crayford wrote:
> No worries. FWIW, I think using the // modulo operator would make
> your code less verbose and complex ;)
>
> On 2020-04-28 11:14 AM, CM Poncelet
/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of CM
Poncelet [ponce...@bcs.org.uk]
Sent: Monday, April 27, 2020 11:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
Thanks, but I
Thanks - I have figured out how to use it.
It's an edit macro and it must therefore be saved with an ".spf"
extension instead of the ".isp" one used for CTC Rexx execs. Also, it
needs to be invoked while editing a file and not issued as a TSO
command. When all that is done, it works OK.
Thanks
On 2020-04-28 03:47, CM Poncelet wrote:
Thanks, but I get the following errors:
ecalc(182): Error #39, Evaluation stack overflow
do until tmp = tail
PRESS ANY KEY TO CONTINUE.
and
Error 10: Illegal ISPEXEC Service 'isredit macro (parm) NOPROCESS'.
PRESS ANY KEY TO CONTINUE.
No worries. FWIW, I think using the // modulo operator would make your
code less verbose and complex ;)
On 2020-04-28 11:14 AM, CM Poncelet wrote:
Yes, you are absolutely right. I thought it was the other way round,
divisble by 100 being leap years and by 400 not leap years.
It should have
Thanks, but I get the following errors:
ecalc(182): Error #39, Evaluation stack overflow
do until tmp = tail
PRESS ANY KEY TO CONTINUE.
and
Error 10: Illegal ISPEXEC Service 'isredit macro (parm) NOPROCESS'.
PRESS ANY KEY TO CONTINUE.
I have CTC Rexx running under DOS - perhaps
Yes, you are absolutely right. I thought it was the other way round,
divisble by 100 being leap years and by 400 not leap years.
It should have been
LEAP = (YEAR-YEAR%4*4=0 & YEAR-YEAR%100*100¬=0 | YEAR-YEAR%400*400=0)
This does not affect the calculations themselves, but it does report
ussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Monday, April 27, 2020 1:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
On Mon, 27 Apr 2020 17:10:54 +, Seymour J Metz wrote:
On Mon, 27 Apr 2020 17:10:54 +, Seymour J Metz wrote:
>> I hope not.
>
>What do you have against ETOD?
>
>> TIME macro
> TIME STCKE,foo
>
>Or doesn't that do the adjustments?
>
I believe it does not. I believe TIME LOCAL and TIME GMT do.
I believe STCKCONV and CONVTOD do not. I am
behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Monday, April 27, 2020 10:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
On 2020-04-27, at 04:57:13, Seymour J Metz wrote:
>
> Is there a statement of direction fo
On Mon, 27 Apr 2020 17:01:08 +0800, David Crayford wrote:
>FYI, you have a bug with your leap year calculation. You need to check
>if the year is evenly dividable by 100 (which are not leap years unless
>evenly divisible by 400).
>
>isleap: procedure
> arg year .
> return (year // 4 = 0 &
On 2020-04-27, at 04:57:13, Seymour J Metz wrote:
>
> Is there a statement of direction for using ETOD for all timestamping?
>
I hope not.
I once went to SR because the timestamps in IEBCOPY SYSPRINT were
about 20 seconds ahead of those in job log. Suggested I suspected
a leap second problem.
On 2020-04-24 06:01, CM Poncelet wrote:
I attach a Rexx program to calculate and display the biorhythm values
for a given date of birth and current or whatever other date.
And if you want to see some niche graphs, try "ecalc biog(dd.mm.)", where
ecalc can be found (for now) @
, April 27, 2020 5:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
On 2020-04-27 5:18 PM, Ray Pearce wrote:
> Will there be a Y2.1K bug?
I don't know but we've got much bigger problems to solve before then
when the TOD clocks start wrapp
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of David Crayford
Sent: 27 April 2020 10:38
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
On 2020-04-27 5:18 PM, Ray Pearce wrote:
Will there be a Y2.1K bug?
I don't know but we've got much bigger
Subject: Re: Friday OT, cheerful program for gloomy times
On 2020-04-27 5:18 PM, Ray Pearce wrote:
> Will there be a Y2.1K bug?
I don't know but we've got much bigger problems to solve before then
when the TOD clocks start wrapping :).
Hopefully, I will be reti
צ
בתאריך יום ב׳, 27 באפר׳ 2020, 12:38, מאת David Crayford <
dcrayf...@gmail.com>:
> On 2020-04-27 5:18 PM, Ray Pearce wrote:
> > Will there be a Y2.1K bug?
>
> I don't know but we've got much bigger problems to solve before then
> when the TOD clocks start wrapping :).
>
> Hopefully, I will be
On 2020-04-27 5:18 PM, Ray Pearce wrote:
Will there be a Y2.1K bug?
I don't know but we've got much bigger problems to solve before then
when the TOD clocks start wrapping :).
Hopefully, I will be retired by then.
--
For
: Friday OT, cheerful program for gloomy times
FYI, you have a bug with your leap year calculation. You need to check
if the year is evenly dividable by 100 (which are not leap years unless
evenly divisible by 400).
isleap: procedure
arg year .
return (year // 4 = 0 & year // 100
FYI, you have a bug with your leap year calculation. You need to check
if the year is evenly dividable by 100 (which are not leap years unless
evenly divisible by 400).
isleap: procedure
arg year .
return (year // 4 = 0 & year // 100 /= 0 ) | year // 400 = 0
On 2020-04-24 2:01 PM, CM
ist [IBM-MAIN@LISTSERV.UA.EDU] on behalf of CM
Poncelet [ponce...@bcs.org.uk]
Sent: Sunday, April 26, 2020 3:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
Mike Cowlishaw created the Rexx language
https://secure-web.cisco.com/1wHB0OokqTuD1qCScSXs4v
Mike Cowlishaw created the Rexx language
https://en.wikipedia.org/wiki/Mike_Cowlishaw
On 26/04/2020 15:48, Paul Gilmartin wrote:
> On Sun, 26 Apr 2020 07:39:27 +, Seymour J Metz wrote:
>
>> They say that the memory is the second thing to go; I don't remember the
>> first thing.
>>
>>
On Sun, 26 Apr 2020 07:39:27 +, Seymour J Metz wrote:
>They say that the memory is the second thing to go; I don't remember the first
>thing.
>
>Given that Mike Cowlishaw was involved in developing ANSI X3.274-1996, I'm
>pretty sure that he would claim that to be the standard Rexx
on behalf of
Joel C. Ewing [jcew...@acm.org]
Sent: Sunday, April 26, 2020 10:03 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
On 4/25/20 3:51 PM, Paul Gilmartin wrote:
> I did not copy-and-paste; I downloaded the attachment,
> which app
On 4/25/20 3:51 PM, Paul Gilmartin wrote:
> I did not copy-and-paste; I downloaded the attachment,
> which appears to be UTF-8.
>
> For Regina, Regina.pdf says: 3.1.1.1 Negators
> ... Regina supports the following characters as negators:
> ...
> ¬ Logical Not
> Copy-and-paste from the
, April 25, 2020 11:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
"ON NO VALUE" from memory.
"supports the standard Rexx language" as per Mike Cowlishaw's definition
(COW).
Comparison of Built-In Functions
The foll
_
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Saturday, April 25, 2020 7:10 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Friday OT, cheerful program for gloomy times
>
> Have you checked tha
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
Always curious about compatibility issues, copied program and pasted
into gedit on Fedora Linux, put a leading
"#!/usr/bin/rexx" and tried to run with oorexx on linux. Only code
issues found:
(1)Not rea
.uk]
Sent: Saturday, April 25, 2020 7:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Friday OT, cheerful program for gloomy times
Have you checked that your version works, other than on a mainframe?
After commenting out the "SIGNAL ON NO VALUE" because it produces a
"LABEL NOT FO
Have you checked that your version works, other than on a mainframe?
After commenting out the "SIGNAL ON NO VALUE" because it produces a
"LABEL NOT FOUND", I ran it and got:
bio2(50): Error #40, Incorrect call to routine
FACTOR1 = DATE( 'Base', YEAR || MONTH || DAY, 'Standard' )
PRESS ANY KEY
Nice one. (BTW My version was not "optimised": it worked and that was
enough.)
Your NUMERIC DIGITS 8 *might* not be sufficient for your "finite
difference equation to generate table of sines". I used the much slower
Taylor series for calculating sines, for which NUMERIC DIGITS 100 worked
"OK" -
'DATE1' must be no later than end date 'DATE2'.'
SAY ' '
SAY 'Please try again.'
SAY ' '
CALL EXIT
END /* IF */
/* CHECK THAT DATE1 DATA IS VALID AND WHETHER LEAP YEAR ETC. */
Q = DATE1
CALL CHECK_DATE
/* CONVERT DATE1 YEARS, MONTHS, DAYS TO FACTOR */
FACTOR1 = DATE( 'Base', YEAR || MONTH |
The attachment was in Windoze's "text document" ANSI format. Not sure
what code page that is other than it's the "UK" one (not pure ASCII.)
When I copied the original BIO.ISP to BIO.txt, all the "¬" (ASCII x'AA')
were changed to "ª" in Windoze. So I replaced all the "¬" with "@" in
SPF/PC then, in
On Sat, 25 Apr 2020 18:10:25 +1000, Wayne Bickerdike wrote:
>Paul asked:
>
> *What code page was your attachment?*
>
>It's US Code page 37.
>
Is that an EBCDIC code page? The attachment looks more
like ASCII, or UTF-8.
Blame the editor. TextEdit fails to show the "¬"; BBEdit fails to show the
Always curious about compatibility issues, copied program and pasted
into gedit on Fedora Linux, put a leading
"#!/usr/bin/rexx" and tried to run with oorexx on linux. Only code
issues found:
(1)Not really a code issue, but had to to run through dos2unix to
convert Windows CR LF end-of-line to
Paul asked:
*What code page was your attachment?*
It's US Code page 37.
On Sat, Apr 25, 2020 at 4:30 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Sat, 25 Apr 2020 03:15:12 +0100, CM Poncelet wrote:
>
> >"¬" (NOT)
> >
> I inferred as much. What code page was
On Sat, 25 Apr 2020 03:15:12 +0100, CM Poncelet wrote:
>"¬" (NOT)
>
I inferred as much. What code page was your attachment?
>> On Fri, 24 Apr 2020 07:01:52 +0100, CM Poncelet wrote:
>>> ...
>>> CHECK_DATE:
>>> /* CHECK THAT DATE IS NUMERIC AND IN THE CORRECT FORMAT */
>>> IF DATATYPE(Q,N)
My wife's BIO had a better intellectual quotient than mine today, however,
she dragged me to the shops today at 8:30 to beat the lockdown rush. They
don't open until 13:00 because it's ANZAC day here. I knew I should have
stayed in bed.
On Sat, Apr 25, 2020 at 2:26 PM Wayne Bickerdike wrote:
>
Never thought about it, downloaded to Windoze and it looks like this :
IF DATE2 ¬> DATE1 THEN
CCSID, bah!
On Sat, Apr 25, 2020 at 12:18 PM CM Poncelet wrote:
> Technical support suggests that you try changing your date of birth, to
> see whether that fixes the problem.
>
> On 25/04/2020
Technical support suggests that you try changing your date of birth, to
see whether that fixes the problem.
On 25/04/2020 00:16, Wayne Bickerdike wrote:
> All negatives for me today. Plus I'm thousands of days old :(
>
> On Sat, Apr 25, 2020 at 6:21 AM scott Ford wrote:
>
>> Nice Chris, at least
"¬" (NOT)
On 25/04/2020 02:18, Paul Gilmartin wrote:
> On Fri, 24 Apr 2020 07:01:52 +0100, CM Poncelet wrote:
>
>> I attach a Rexx program to calculate and display the biorhythm values
>> for a given date of birth and current or whatever other date.
>>
>> If 'management' complains that home
On Fri, 24 Apr 2020 07:01:52 +0100, CM Poncelet wrote:
>I attach a Rexx program to calculate and display the biorhythm values
>for a given date of birth and current or whatever other date.
>
>If 'management' complains that home workers are not putting enough
>effort into their working-from-home
Anything with date algorithms floats my boat. Another lot to add to my
list. Thanks!
On Sat, Apr 25, 2020 at 9:16 AM Wayne Bickerdike wrote:
> All negatives for me today. Plus I'm thousands of days old :(
>
> On Sat, Apr 25, 2020 at 6:21 AM scott Ford wrote:
>
>> Nice Chris, at least you have
All negatives for me today. Plus I'm thousands of days old :(
On Sat, Apr 25, 2020 at 6:21 AM scott Ford wrote:
> Nice Chris, at least you have a job, I got furloughed ...
>
>
>
>
> On Fri, Apr 24, 2020 at 2:01 AM CM Poncelet wrote:
>
> > I attach a Rexx program to calculate and display the
Nice Chris, at least you have a job, I got furloughed ...
On Fri, Apr 24, 2020 at 2:01 AM CM Poncelet wrote:
> I attach a Rexx program to calculate and display the biorhythm values
> for a given date of birth and current or whatever other date.
>
> If 'management' complains that home workers
THEN DW1 = '(WEDNESDAY)'
WHEN DW1 = 5 THEN DW1 = '(THURSDAY)'
WHEN DW1 = 6 THEN DW1 = '(FRIDAY)'
OTHERWISE NOP
END /* SELECT */
SAY 'WE HAVE YEAR = 'YEAR', MONTH = 'MONTH', DAY = 'DAY' 'DW1
SAY ' '
/* CHECK THAT DATE2 DATA IS VALID AND WHETHER LEAP YEAR ETC. */
Q = DATE2
CALL CHECK_DATE
ERV.UA.EDU
Sent: Wednesday, July 24, 2019 4:58:11 PM
Subject: Re: Friday!
You had switches? We had to hard-wire the cores...
On Mon, Jul 22, 2019 at 11:01 AM Carmen Vitullo wrote:
> same here, but on a Univac processor we had in school, all done by
> switches.
>
1 - 100 of 419 matches
Mail list logo
