I have been getting S0C4 on initialization to my Metal C program
Once again, you have not provided enough information for most of the
readers of your post to help you.
Not every "Prolog code of Metal C program" has such a store of register 0.
This is easily demonstrated.
Thus perhaps you in s
I have code on windows that I use to display assembler listing. I down load
the SYSADATA and have a DLL that does reads and does various other
functions. Since I have a need for the same functionality on z/os I figured
I would use the same code.
I knew there would be differences but I figured I co
Dean,
I have to agree with Ken, have you actually looked at small replicated
Virtual-Tape solutions on a price point? You say "The C07 is the controller..."
- indicating you might only have one (or a second one for backup); which would
then mean you probably only have 8 to 16 drives. While the
Dean,
Sorry, I had been on vacation a good part of last week. With CA 1, the CTSSYNC
utility has a "SYNCTEST" that basically does the same thing. It validates all
three databases (the OAM/TCDB, CA 1's TMC, and the Library Managers database)
against each other. If any 1 is out-of-sync with the o
Hi Dean
For what you are looking for the Visara VI-5990 would fit the bill.
Ken
Kenneth A. Bloom
Avenir Technologies Inc
/d/b/a Visara International
203-984-2235
bl...@visara.com
www.visara.com
> On Jan 26, 2020, at 11:54 AM, Russell Witt
> <025adb32e6d7-dmarc-requ...@listserv.ua.edu> wr
I wrote a program -- robust enough to be part of a vendor product -- that
read and processed assembler SYSADATA using LE-supported C++. I found no
problems with "flexibility." I would be curious in what way you found it
inflexible.
As is my general approach with C++, I did alpha testing on MS Visu
I had the sysadata downloaded as binary
And had the ebcdictoascii routine
And as you are correct for the length and offset pointers I had a bigedcpy
routine to copy it to a int to make sure it was aligned correctly
In the mainframe I store sysadata in a dataspace and Metal seems perfectly
Well, I hear you.
A dataspace seems like overkill. How much data do you have?
My program runs 31-bit and keeps its data just in C++ "new" storage (GETMAIN
storage, in the region) and I never heard of any issue, not even an x78 ABEND
where the answer was "increase the region size." I suppose sup
I down loaded the look program from the CBT site it generated huge amounts of
sysadata as it maps many or most z/os control blocks having a pointer to symbol
type record is a lot quicker the reading the VB file
Correct me if I am wrong but total number of records are at the end of the file
rec
I believe you. The input for my program tends to be relatively smaller
assemblies.
> Correct me if I am wrong but total number of records are at the end of the
> file record type Two
Could be. That is how I read the following:
Record Count FL4 On an ADATA Compilation Unit End record, a count o
10 matches
Mail list logo
