There are chapters in various RedBooks that give you more information, but once
you have ARX Running with the System REXX Libraries defined you are running in
an AUTHORIZED REXX environment that is secured by SAF (your RACF, TopSecret, or
whatever). Programming REXX for System REXX adds a few System REXX Commands
(access to the console, wait, get replies to console messages); but unless you
are writing a Health Check, its is almost straight REXX code (very similar to
OPSMVS REXX, with OPS prefixed commands replaced by IBM REXX and System REXX
Commands that are almost parameter equivalent).
From a slightly modified the MPF Exit Sample (see the chapter you mentioned on
Calling System REXX) you can:
- Call a MVS REXX (no TSO Available, but not restricted to 4-8 TSO threads,
and with BPXWDYN for allocations, not much you cannot do)
- Call a TSO REXX very similar to what most of OPSMVS runs in, so
relatively easy to convert
- You have access to the System Console, SDSF, and USS; plus everything you
can do via REXX with those
- If you want, and see an automation need, you can also write a REXX based
Health Checker component (Health Checker seems a better interface for some
automation)
If you use OPSMVS’s SSM feature, it is basically:
— A database of STCs, Messages, and REXXes to manage them
— An interface for managing this Database
One way to replace this is by using SQLite3 (https://sqlite.org). You can
compile this yourself using the Amalgamation Source from the SQLite website, or
CBTTape.org’s File 965 (if you do not have access to the IBM C Compiler). Any
DBA would be able to help you develop the Schema (Data Definition Statements)
to set up the 2-3 Databases that would duplicate those in SSM. The SQL calls
are all very similar to coding in OPSMVS SSM Rules (they use formal SQL, but
you can tell they do the same thing).
Another would be to use the REXX VSAM Interface in CBTTape.org’s File 268 (a
little less capable then a full Relation Database, but if you are more familiar
with VSAM the SQL, I have used this under NetView to build a SSM equivalent
back in the mid 1990’s using Netview REXX).
I don’t think I contributed any of my Health Checker or SQLite Sample REXXes to
CBT File 960, but I do have a number of them if you are interested (I can sen.d
them offline).
_______________
Al Ferguson | mailto:[email protected]
Milwaukee, WI USA | http://www.neptunescove.org
Dulcius ex Asperis
> On 07 February 2020, at 11:56, Gibney, Dave <[email protected]> wrote:
>
> Is there more documentation on System Rexx besides that short chapter in Auth
> Assembler Services?
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List <[email protected]> On
>> Behalf Of Al Ferguson
>> Sent: Friday, February 07, 2020 9:48 AM
>> To: [email protected]
>> Subject: Re: Downsizing? - OPS?
>>
>> Another solution might be to use System REXX in combination with MPF (the
>> Message Processing Facility). IBM provides a sample MPF Exit that will call
>> System REXX Passing it the MPF Message Number and Message Text. A few
>> more generic MPF entries using that Exit to call various decision REXXes that
>> would either do simple automation for a class of messages, or call another
>> System REXX to do more complex automation would handle much of the
>> System Automation.
>>
>> The nice things with a System REXX and MPF solution:
>> - They are both part of the Base System (IBM Supports them & you have
>> them for no additional $’s)
>> - They are up early in an IPL and shut down late during shutdown (so are
>> there for most automation)
>> - You have access to TSO (when needed) or just MVS (and OMVS)
>> - You can do most of it in REXX (most likely very similar REXX EXECs as
>> available in OPSMVS)
>>
>> _______________
>>
>> Al Ferguson | mailto:[email protected]
>> Milwaukee, WI USA | https://urldefense.proofpoint.com/v2/url?u=http-
>> 3A__www.neptunescove.org&d=DwIFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk
>> 4EJm8LdrrvxQb-Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=KN-
>> T011gdEnU1Kwzdq_xDtDCiXu1gRfiry1tImk-aaI&s=uNHJWas-
>> kBNLuPvtpOmfLWHlpVgswdsboZHk1KewyAo&e=
>>
>> Dulcius ex Asperis
>>
>>> On 07 February 2020, at 06:26, Lionel B Dyck <[email protected]> wrote:
>>>
>>> For an automation tool at no cost, other than your time/resources,
>>> take a look on the cbttape at TSSO - it works with z/OS, is free, and
>>> does some of what OPS does - perhaps most since you can write your own
>> rexx for it.
>>> Balance the cost of your time/resources with the cost of a vendor
>>> product and as usual ymmv.
>>>
>>> Good luck
>>>
>>>
>>> Lionel B. Dyck <sdg><
>>> Website:
>>> https://urldefense.proofpoint.com/v2/url?u=http-
>> 3A__www.lbdsoftware.co
>>> m&d=DwIFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-
>> Je7sw&r=u9g8rUevBoy
>>> CPAdo5sWE9w&m=KN-T011gdEnU1Kwzdq_xDtDCiXu1gRfiry1tImk-
>> aaI&s=kXNlhWRhwp
>>> Eu7WqRkjLuO-Y7y-ebLHXJdImeFqOwdMU&e=
>>>
>>> "Worry more about your character than your reputation. Character is
>>> what you are, reputation merely what others think you are." - John
>>> Wooden
>>>
>>> -----Original Message-----
>>> From: IBM Mainframe Discussion List <[email protected]> On
>>> Behalf Of Gibney, Dave
>>> Sent: Thursday, February 6, 2020 8:00 PM
>>> To: [email protected]
>>> Subject: Downsizing? - OPS?
>>>
>>> The direction is clearly set. My z/OS 2.1 installation is heading
>>> for a sunset, sometime in the next several years. The Student Systems
>>> were ERP's to cloud systems not quite a decade ago. The remaining
>>> (HR/Financial/Etc.) are scheduled for migration to Workday (again, in cloud)
>> July 1.
>>> There is still archive/historical data that wasn't moved and more
>>> that isn't moving. There is a need/plan to run reduced/read-only for
>>> an as yet undetermined time. We moved our 4 LPARs (Production,
>>> Development, 2
>>> sandboxes) to a MFaaS provider at the end of 2017. Part of the plan is
>>> to reverse the path we took from 1 LPAR to 4 LPARS, back to 1 LPAR.
>>>
>>> Now, I need to plan to reduce the footprint expenses. In
>>> particular, we probably won't be renewing ISV contracts.
>>> I have z/OS alternatives to some (DF/SORT, DFSMSrmm, etc.) And,
>>> z/OS is part of the MFaaS contract. Although we do plan to consolidate
>>> LPARs and reduce the overall footprint.
>>>
>>> Which brings me to my question and request for advice. Given the
>>> constraints (free or native z/OS 2.1) what alternatives to CA-OPS
>>> would the community recommend. I know there's some in the firehose
>>> that is https://urldefense.proofpoint.com/v2/url?u=http-
>> 3A__www.cbttap.org&d=DwIFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8Ld
>> rrvxQb-Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=KN-
>> T011gdEnU1Kwzdq_xDtDCiXu1gRfiry1tImk-aaI&s=bZe-
>> U_AAzWvh7xppHTg9iaGyKSoQm4T2H8RPvEwb74Y&e=
>> <https://urldefense.proofpoint.com/v2/url?u=http-
>> 3A__www.cbttap.org&d=DwIFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8Ld
>> rrvxQb-Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=KN-
>> T011gdEnU1Kwzdq_xDtDCiXu1gRfiry1tImk-aaI&s=bZe-
>> U_AAzWvh7xppHTg9iaGyKSoQm4T2H8RPvEwb74Y&e= >.
>>>
>>> I eventually need to leave WSU (in about a year) with a system that
>>> can coast 3 to 7 years with minimal skilled care.
>>>
>>> Dave Gibney
>>> Information Technology Services
>>> Washington State University
>>>
>>>
>>> ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions, send
>>> email to [email protected] with the message: INFO IBM-MAIN
>>>
>>> ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions, send
>>> email to [email protected] with the message: INFO IBM-MAIN
>>>
>>
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
>> [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
