Just wanted to add to my earlier post. The disassembler provided with the
Assembler Toolkit is now part of HLASM and shipped as load module ASMADOP
in SYS1.MIGLIB. Looks like this was done with APAR PQ27453 back in 1999!
Regards,
Peter Van Dyke
HCL Software
On Wed, 9 Dec 2020 at 10:54, Mike
There is always the approach of running the program. ABEND S0C1 indicates
that you need a newer box (or better programmers).
I suppose an arguably good corporate standard might be to require embedding
the required ARCH level in programs as a readable EBCDIC constant.
Charles
-Original
Thanks.
I am going to just live with my own declaration. I am too busy with real work
to debug dirent.h.
Thanks again,
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jantje.
Sent: Monday, December 7, 2020 9:05 AM
To:
Hello-
I am creating a dynamic SFTP sortcard using DFSORT, here in the Input file the
Store_nbr is at position 40. I need the file to created as
SPUT 'K01.BB.RST.PTEM.FUTR.RTLDTA.REPT01' FUTRETAIL_2020-12-07_33.csv
but the issue is the store_nbrs are of different length, the .csv is not
i thought MVS/XA was CBIPO?
Joe
On Tue, Dec 8, 2020 at 2:04 PM Mark S Waterbury <
01c3f560aac1-dmarc-requ...@listserv.ua.edu> wrote:
> Hi, all,
>
> Does anyone recall how MVS/XA was first distributed and installed? e.g.
> was there some kind of a "starter system"? If so, what was it?
If I remember correctly the vaul pattern is defined in the VRS.
On Monday, December 7, 2020, 02:04:24 p.m. EST, Lizette Koehler
wrote:
Did you look in ISMF Option G Reports?
I think there are some in there
Lizette
-Original Message-
From: IBM Mainframe Discussion List On
> but the issue is the store_nbrs are of different length, the .csv is
> not getting created correctly . Could some one let me know how we
> can append the .csv also when the store is of variable length
>
Ron,
Try this DFSORT JCL
//STEP0100 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SORTIN DD *
I installed MVS/XA under using our existing MVS/SP V1 system. For a new MVS
customer I assume that IBM shipped a starter system like they do now which was
a stripped down OS with just enough "stuff" to install the MVS/XA system.
As for your optional source material question, I don't remember,
I kinda remember MVS/XA and later ESA being CBIPO and CBPDO for maint.
SYSGEN I think was still needed for XA and maybe ESA.
I'm not sure what you meant by Optional Source Materials. If by that you
meant optional source code to install, I think they went the microsloth
bloat ware option
ISTR there was also a special version of VM/XA made available "early" so that
customers could run both 24-bit MVS/SP and 31-bit MVS/XA on the same physical
machine.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Brian France
Sent: Tuesday, December 8, 2020
Hi, all,
Does anyone recall how MVS/XA was first distributed and installed? e.g. was
there some kind of a "starter system"? If so, what was it? MVS 3.8J, or
MVS/SE or MVS/SP or what?
I seem to recall that someone told me that there was no longer any "SYSGEN"
process used to install MVS/XA?
It was ordered and installed using the CBIPO proceess, but the install needed
to run on an existing MVS system.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
‐‐‐ Original Message
Yes, and I believe the "driving' system for install had to be MVS/SP or
higher...
Joe
On Tue, Dec 8, 2020 at 3:11 PM Brian France wrote:
> I kinda remember MVS/XA and later ESA being CBIPO and CBPDO for maint.
>
> SYSGEN I think was still needed for XA and maybe ESA.
>
> I'm not sure what you
The *fun* memories of a POR before every time we tested MVS/XA and then another
one when we went back to MVS/SP for production just returned.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
In my first shop we did a conversion from OS/VS1 straight to MVS/XA (IBM made
us an offer we couldn't refuse). This was a little before CBIPO so first had
to lay down a starter system that was some flavor of MVS/370 or /SP. I say
that because it ran under our VM/SP (actually HPO) system.
For those new to MVS there was the MVS/XA Express option. You have to qualify
to get it. A shop I worked at a long time ago was a VSE shop that was going to
convert to MVS and that is how we started off. I believe the MVS/XA Express
was a complete IPL system that IBM built based on your
Oops, got the hardware lvl for AHI wrong, so changed 'G9' to 'G10'
Hi,
I'm looking for a utility/program which is capable of reading a z/OS
executable, whether an lmod or program object, or unbound object code, and
examining it for hardware/architecture level compatibility. I'm not
Just catching up. You may be referring to “XPROC” which is on file 772 of the
CBT tape, which I’ve used in private rexx execs.
Wayne Driscoll
Rocket Software
Note - All opinions are strictly my own.
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, November 19,
It's not foolproof, but for both HLL's and assembler the COBANALZ program in
CBT file 321 will give you (in the SUMMARY DD output) a pretty good guess at
the compiler or assembler version that generated the code. From that you could
extrapolate the minimum hardware level required based on the
As one who has actually used the Assembler Toolkit disassembler for "lost
source, lost listings" cases, I would warn anyone looking to use it that it
requires quite a lot of customization and experimentation with multiple utility
options for each executable you need to analyze, and many
Paul,
Thank you for that memory jog. Yep, it was MVS/Express. It was a stand-alone
restore tape of MVS/XA (ours was 2.1.7) that once restored was an IPLable XA
system - and reasonably current on maintenance.
Fun time was going to a class for MVS newbies and using the MVS/express tape.
8
"Version of the compiler" is not sufficient to answer "what hardware level
is required?" For example, COBOL 6.3 lets you specify ARCH() 8, 9, 10, 11,
12 or 13. So the object code might run on a z10, or it might require a z15,
or anything in-between.
Charles
-Original Message-
From: IBM
True, and also true for the XLC and PL1 compilers. I did say "crude", and I
meant it.
OTOH, if the executable is an HLL from one of the more recent compiler levels
which use LE control blocks, ARCHLVL output can be found (or added to) the very
detailed HLL information that CONANALZ can/could
You could use PUTs for maintenance, and most shops did. While you could freeze
the system for a long time and then install a new IPO or PDO, that wasn't the
norm.
Sysgen wasn't needed once MVSCP was available, and it eventually went away.
When you ordered IBM software, certain items were
Hi,
I'm looking for a utility/program which is capable of reading a z/OS
executable, whether an lmod or program object, or unbound object code, and
examining it for hardware/architecture level compatibility. I'm not
specifically referring to the ARCLVL of on the SYSSTATE macro, although I know
I ran these CBIPO installs in the early eighties. I am pretty sure it used
SMP/E to perform the generation using the GENERATE command.
I had an MVS/SP driving system of course. The first MVS/XA system I built was
XA 2.1.2 I think.
Lennie Dymoke-Bradshaw
Consultant working on contract for BMC
So the utility would loop through the object code looking for opcodes, and
when it found one it would know the required hardware level, and keep track
of the maximum found?
Interesting idea. I have never heard of such a utility, but it could be
attempted. Finding op codes is an imperfect science
If there isn't a ready made solution available, the High Level Assembler
Toolkit has a disassembler utility which could provide the input to a new
tool that scans the assembler instructions and matches them to the hardware
level. The IBM File Manager 'View Load Module' or VLM function can also
GENERATE rebuilds the target datasets from the distribution data sets; you
still need an MVS/SP system generation or MVSCP to define the I/O
configuration. I don't recall IPO ever using GENERATE, but memory is the second
thing to go.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
Some new feature added new bit to, e.g., control registers, parameters, tables.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Peter Van Dyke [pdvand...@gmail.com]
As I recall MVS, Express was tailored to your I/O configuration, so you had
more flexibility in your IOCDS.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Feller,
Yeah, disassemblers are not magic. There is a loss of information going from
source code to object code, and there is no tool that magically makes that
information reappear.
I am not familiar with File Manager. I am looking at example "Load Module
Information" for a load module compile with
XPROC sounds right. Thanks.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Wayne Driscoll [wdrisc...@rocketsoftware.com]
Sent: Tuesday, December 8, 2020 5:48 PM
To:
VM/XA MA was the first VM/XA, so I wouldn't call it special.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Farley, Peter x23353
Is the facility to check for the facility bits often present in load
modules? I. E. a certain opcode or SVC call? Then hou could look at
the bits being checked.
On Tue, Dec 8, 2020 at 6:11 PM Seymour J Metz wrote:
>
> Some new feature added new bit to, e.g., control registers, parameters,
>
There is certainly code that uses, e.g., STFLE, and checks the result.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Mike Schwab [mike.a.sch...@gmail.com]
Sent:
You needed an MVS driver system to install MVS/XA. Most customers already had
an existing MVS/SP system, and didn't need to order the starter system. IPO and
PSO were available later. Optional souce was available on tape. There was no
PTF optional source; if the module was hit by service, you
Yes, IPO used generate.
There was IPOUPDTE and IPOGEN.
http://www.computinghistory.org.uk/downloads/9653
Joe
On Tue, Dec 8, 2020 at 6:08 PM Seymour J Metz wrote:
> GENERATE rebuilds the target datasets from the distribution data sets; you
> still need an MVS/SP system generation or MVSCP to
AFAIK tape is no longer an option. There used to be a DVD option; I don't no
whether it is still available. The normal vehicle for product and service these
days is the Internet.
The basic process is still the same; if you don't have a driver system, you
need to restore a starter system and
On Wed, 9 Dec 2020 01:50:32 +, Jesse 1 Robinson wrote:
>We have downloaded ServerPac for years entirely from the network. No need for
>tape.
>
What would one use to access the network?
>
On Wed, 9 Dec 2020 02:12:11 +, Seymour J Metz wrote:
>
On Wed, 9 Dec 2020 00:48:31 +, Seymour J Metz wrote:
>You needed an MVS driver system to install MVS/XA. Most customers already had
>an existing MVS/SP system, and didn't need to order the starter system. IPO
>and PSO were available later. Optional souce was available on tape. There was
We have downloaded ServerPac for years entirely from the network. No need for
tape.
.
.
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-
Thanks all, yet again, for all the excellent ideas! These IBM- listservs are a
truly fine resource. ('the power of many brains working!') I will probably end
up doing some flavor of opcode evaluation, and assumed, maybe erroneously, that
opcode evaluation would be simpler/cleaner to implement
43 matches
Mail list logo
