Thank you all.
I will do my research and get back to you if I have any questions.
On Fri, 25 Dec, 2020, 3:43 am Longnecker, Dennis, <
dennis.longnec...@courts.wa.gov> wrote:
> We did this migration not too long ago. It was actually pretty easy once
> everything was setup and the devices were av
It's an OS/2 port of a standard Enunix command. Run cp --help on any *ix system
and you'll get essentially the same text, with whatever path it's running from.
My spelling is a comment on the Multics features that Unix doesn't have.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
The period is a valid character in Eunix file names, and many programs
construct names containing periods.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
David Spiegel
It's a shame that IBM doesn't push the boundaries during Alpha testing.
I have a dream of a testing laboratory with a large pool of users who know
nothing about the product. That would be especially valuable for testing the
documentation.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz
LOL I was going to say, "Because it's there"
On 12/24/2020 3:38 PM, Tom Conley wrote:
On 12/24/2020 12:01 PM, Ed Jaffe wrote:
On 12/22/2020 6:09 AM, Joseph Reichman wrote:
Thanks I’m not writing RMODE64 code don’t see a reason to > > I
don’t know why Ed co. does cann’t believe the code is tha
And if there is a "there" there, Ed will find in a jaffe
Chris Hoelscher
Lead Sys DBA
IBM Global Technical Services on assignmemt to Humana Inc.
T 502.476.2538 or 502.407.7266
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Tom
Conley
Sent: Thursday, December 24,
On Thu, 24 Dec 2020 09:01:40 -0800, Ed Jaffe wrote:
>
>We are writing an RMODE(64) product because we love z/OS and wish to
>help push the boundaries of its technological limitations wherever we can.
>
IBM hates people like that.
At a SHARE meeting (where I believe I met you), John E. (FSVO "E")
We did this migration not too long ago. It was actually pretty easy once
everything was setup and the devices were available on all LPARs.
The main tool we used was FDRCOPY. With a few simple jobs, we were able to use
it and migrate almost 80% of the items on the TS7720 to the DLM. It did the
On 12/24/2020 12:01 PM, Ed Jaffe wrote:
On 12/22/2020 6:09 AM, Joseph Reichman wrote:
Thanks I’m not writing RMODE64 code don’t see a reason to > > I don’t
know why Ed co. does cann’t believe the code is that large
> Thanks for the heads up about LE
We are writing an RMODE(64) product becau
Hi Gil,
It's not UNIX for more than one reason:
- UNIX has no drive letter
- UNIX uses a forward-slash, not, a backward-slash
- UNIX does not have File Extensions (although theoretically it could)
Regards
David
On 2020-12-24 17:58, Paul Gilmartin wrote:
On Thu, 24 Dec 2020 22:14:15 +, Seymo
On Thu, 24 Dec 2020 22:14:15 +, Seymour J Metz wrote:
>Eunix has even less typing:
>
>Thu 12-24-20 12:49:37{2}[h:\] cp --help
>Usage: G:\USR\BIN\cp.exe [OPTION]... [-T] SOURCE DEST
> or: G:\USR\BIN\cp.exe [OPTION]... SOURCE... DIRECTORY
>
That doesn't look much like UNIX to me. I guess that
On Thu, 24 Dec 2020 16:02:07 -0500, Steve Thompson wrote:
>So write a PROC that puts INPUT with SYSUT1 and OUTPUT with SYSUT2.
>
I could imagine that nowadays TRSMAIN is merely an ALIAS entry point that
branches to AMATERSE with an alternate DDNAME list.
>I even took this a step further and had
Eunix has even less typing:
Thu 12-24-20 12:49:37{2}[h:\] cp --help
Usage: G:\USR\BIN\cp.exe [OPTION]... [-T] SOURCE DEST
or: G:\USR\BIN\cp.exe [OPTION]... SOURCE... DIRECTORY
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainfra
So write a PROC that puts INPUT with SYSUT1 and OUTPUT with SYSUT2.
I even took this a step further and had OUTPUT get deleted first before
AMATERSE.
Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct
mistaks
> On Dec 24, 2020, at 3:56 PM, Paul Gilmartin
> <00
On Wed, 23 Dec 2020 15:40:23 +, Pommier, Rex wrote:
>
>Yeah there's a problem with it - a human problem. It's easy when in a hurry
>to miss the fact they're reversed and key the input dataset name in the SYSUT2
>and the output in the SYSUT1 if you're not paying attention. Yeah I know it's
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Except move is propogate a copy. CA IDEAL has MOVE A TO B and SET B = A.
Interchangeable but one is linguistically confusing. Less typing too!
On Thu, Dec 24, 2020, 05:51 Seymour J Metz wrote:
> I find move source destination to be more natural than move destination
> source.
>
> "When the only
We decided not to do that and go with a TS7760 instead. Easy peasy
Roger W. Suhr
suhr...@gmail.com
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Peter
Sent: Wednesday, December 23, 2020 11:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TS7720 to EMC DLM migration
I've been ftping files to testcase.boulder.ibm.com all morning and all of a
sudden they started failing with:
EZA2590E send error from send_data - EDC5140I Broken pipe. (errno2=0x74520442)
EZA2603E Error sending the file
EZA25
The new platform is mainframe Java
Nobody cares about dinos
> On Dec 24, 2020, at 12:36 PM, Paul Gilmartin
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
> On Thu, 24 Dec 2020 08:44:09 -0800, Charles Mills wrote:
>
>> I would never presume to tell IBM what to do, but if I were r
> The cost of providing adequate documentation should be factored
into the business case for new features, not used as an excuse for
not providing it.
AMEN! Well said. Correct documentation is not an optional luxury, it is
fundamental part of the new feature.
Charles
-Original Message
On Thu, 24 Dec 2020 08:44:09 -0800, Charles Mills wrote:
>I would never presume to tell IBM what to do, but if I were responsible for
>the "MVS Services" documentation I would start with a preamble much like
>@Gil describes in which I said "unless otherwise specified, callers must be
>..." and cov
You have received a Vanguard Integrity Professionals Secured Email Server
Message from:
Tony Nix
To read this message securely, click the link below or request that the message
be sent in another format. Vanguard
Integrity Professionals is dedicated to protecting your critical infrastructure
If you look in the IBM MAIN archives for DLM, you should find lots of
information.
I have gone both ways IBM to EMC and EMC to IBM
There are some changes to the way the Library is defined in ISMF>
There are some IOGEN considerations
You should find the vendor you are going to, very helpful in
On 12/22/2020 6:09 AM, Joseph Reichman wrote:
Thanks I’m not writing RMODE64 code don’t see a reason to > > I don’t know why Ed co. does cann’t believe the code is that large
> Thanks for the heads up about LE
We are writing an RMODE(64) product because we love z/OS and wish to
help push the
The migration was complex enough that we engaged a separate third party ISV to
guide us through. This was going from a combination of virtual (STK) and
physical tape 100% DLm. Allow several months.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS
I would never presume to tell IBM what to do, but if I were responsible for
the "MVS Services" documentation I would start with a preamble much like
@Gil describes in which I said "unless otherwise specified, callers must be
..." and covered ASC, SRB/TCB, AMODE, RMODE, problem/supervisor, etc.
It
It is re-entrant have the Rent option and I have global areas
Thanks
> On Dec 24, 2020, at 11:30 AM, Joe Monk wrote:
>
> OK so there's no need for reentrancy. Thus, no need for WSA.
>
> Joe
>
>> On Thu, Dec 24, 2020 at 10:29 AM Joseph Reichman
>> wrote:
>>
>> It’s a batch program calle
In answer to your question, there are plenty of "things to be done", depending
upon factors such as:
- what tape management system do you have? Will the new technology share the
scratch volser range or will a new one be used?
- will the migration be performed volume-by-volume ('cloning') or
dat
OK so there's no need for reentrancy. Thus, no need for WSA.
Joe
On Thu, Dec 24, 2020 at 10:29 AM Joseph Reichman
wrote:
> It’s a batch program called from a started task
>
>
>
> > On Dec 24, 2020, at 11:18 AM, Joe Monk wrote:
> >
> > Still not sure why you have a WSA... Youre not using CICS,
It’s a batch program called from a started task
> On Dec 24, 2020, at 11:18 AM, Joe Monk wrote:
>
> Still not sure why you have a WSA... Youre not using CICS, right?
>
> Joe
>
>> On Thu, Dec 24, 2020 at 10:11 AM Joseph Reichman
>> wrote:
>>
>> This code is right after my prologue
>>
>>
Still not sure why you have a WSA... Youre not using CICS, right?
Joe
On Thu, Dec 24, 2020 at 10:11 AM Joseph Reichman
wrote:
> This code is right after my prologue
>
>
> ST0,#WSA_1
>
> So I have to somehow make sure that register 0 has the right value
>
> Thanks
>
> -Original M
This code is right after my prologue
ST0,#WSA_1
So I have to somehow make sure that register 0 has the right value
Thanks
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Joe
Monk
Sent: Thursday, December 24, 2020 11:04 AM
To: IBM-MAIN@LISTSERV.UA.ED
OK but I dont think you need a WSA.
Joe
On Thu, Dec 24, 2020 at 10:00 AM Joseph Reichman
wrote:
> Thanks I think the problem is my main program is called OPENFILE In this
> program I load sysadata to a dataspace
>
> Why did I use metal C because I have similar C code in windows and thought
> wi
Thanks I think the problem is my main program is called OPENFILE In this
program I load sysadata to a dataspace
Why did I use metal C because I have similar C code in windows and thought with
#pragma if __MVS I could save coding I found it easier to work with Metal then
LE as it gives me more
RMF Monitor III, RMF Resource Report Menu, Storage Usage options.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
‐‐‐ Original Message ‐‐‐
On Thursday, December 24th, 2020 at 1
No. If you are calling METAL C from assembler, METAL C will take care of
the WSA...
"The RENT environment initialization and termination routines are called to
establish and terminate the dynamically allocated WSA storage with the
static initialization data applied. For the AMODE 31 "main" functi
Just read it FYI I am Calling Metal C from Assembler (via Link) Me thinks I
have to init The WSA area Binyamin Dessin suggested I use a CXD variable to
get the size of the WSA
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Joe
Monk
Sent: Thursday, December 24, 2
List -
This is not one of my strong points.
I have RMF and omegamon.
What can I use that will help me over time see what is using all the Page
Datasets or what is being orphaned?
Thanks
Lizette
--
For IBM
This is the code after the prolog don’t see a call WSA initialization
+ LR0,2
+ DROP 15
@@BGN@1 DS0H
AIF (NOT &CCN_SASIG).@@NOSIG1
LLILH 11,X'C6F7'
O
Perhaps you don't understand what I mean by "blanket statement":
a single affirmative sentence in the Introduction to the manual, "Any
service described herein may be invoked from a location below 2 GiB."
Do you think there is anyone in the IBM world who needs that sentence? It
might be thought
Check page 31 in this:
https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc147313/$file/ccrug00_v2r3.pdf
Joe
On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman
wrote:
> I’m writing a prolog for a metal C program
> I noticed that after the prolog code
> Registers 0 is stored in
GPR 0 is used to pass the address of the WSA.
If youre writing a prolog for a Metal C program, you dont need to worry
about the size of the WSA unless you plan to do something with it. The
Metal C program should call the WSA init and term upon entry and exit on
its own.
Joe
On Thu, Dec 24, 2020
I’m writing a prolog for a metal C program
I noticed that after the prolog code
Registers 0 is stored in #WSA_1 seems like storage has to be allocated for it (
writable static area ) in addition to the dynamic storage ( register save +
auto variables )
> On Dec 24, 2020, at 9:32 AM, Peter Rel
I think of the writeable static area as an area that LE instantiates on
your behalf.
As far as I know, there is no interface provided by which you can do this.
If LE is going to do this for you, using loader services that rely on
information within the program object itself (and there is such
i
45 matches
Mail list logo
