ncois Pare
-Message d'origine-
De : IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] De la part de
Brian Westerman
Envoyé : 23 août 2006 22:22
À : IBM-MAIN@BAMA.UA.EDU
Objet : Re: JES2 migration (z/OS 1.4 to z/OS 1.7)
If this is just a matter of moving the spool data to the
If this is just a matter of moving the spool data to the new system as a
one-time thing, then you're Offload is probably the simplest/quickest
method. Otherwise, if you are planning on keeping the old system available
for some short (or long) period of time, I have always found that
connecting
e respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
JES2 migration (z/OS 1.4 to z/OS 1.7)
Hello,
Soon, we're going to migrate from z/OS 1.4 to z/OS 1.7. At the very
precise moment that we do the z/OS migration, we've always done a spool
offload on the
Francois,
As long as you've applied coexistence/fallback service and handled any
documented migration actions for JES2, there should be no need to reformat
your spool for a z/OS 1.4 to 1.7 transition.
Just completed the z/OS 1.7 implementations here this weekend and am on
the same spools as us
On Tue, 2006-08-22 at 11:55 -0400, Francois Paré wrote:
> we've always done a spool offload on the current system and a spool
> reload on the new system. [...] I would like to eliminate this
> task. Do you think it's OK?
Probably okay, but there are a few benefits to doing this (at least in
our
Hello,
Soon, we're going to migrate from z/OS 1.4 to z/OS 1.7. At the very precise
moment that we do the z/OS migration, we've always done a spool offload on the
current system and a spool reload on the new system. I think that it is
probably a task that we do from an old tradition. Since z/
6 matches
Mail list logo
