Microcode is not relevant to your environment. You'd have to first write a
simulator for the hardware that the microcode runs on. Unless you're planning
to hand compile the microcode, you also have to write an equivalent to CAS or
MLS.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
ObPrinessBride What gives you that idea?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Lizette Koehler
Sent: Friday, July 12, 2019 4:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL COND
It's what earned Sade the title Marquis.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List On
COND= was invented by a Sadist.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tom Brennan
Sent: Friday, July 12, 2019 6:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL COND Parameter
I always guessed COND= was
On Sat, 13 Jul 2019 06:53:18 -0700, Lizette Koehler wrote:
>Just a quick summary of the IF THEN ELSE process in JCL. Much easier than COND
>CODE setup
>
I agree.
>The following example shows the use of the alphabetic characters rather than
>special characters for comparison operators.
>
On Fri, 12 Jul 2019 18:08:12 -0700, Tom Brennan wrote:
>I always guessed COND= was invented by someone who took a Boolean Logic
>or Digital Electronics class, where I once heard that negative logic
>NAND/NOR ends up with less logic or hardware than AND/OR.
>
Benjamin Franklin (?) naively and
Just a quick summary of the IF THEN ELSE process in JCL. Much easier than COND
CODE setup
The following example shows the use of the alphabetic characters rather than
special characters for comparison operators.
//IFBAD IF (ABEND | STEP1.RC > 8) THEN
or
//IFBAD IF (ABEND
