Rick, we run two NJE connections from one VM system to two MVS JES2
systems and yes the JES2 end must be defined as BCTC and the VM end must
be defined as SCTC. This is a real PITA when we do DR tests as we always
have to tell the DR provider, Yes, they have to be defined as BCTC.. I
t
Here is an example of IOCP statements for an EMC 8830, (I have one for a
EMC 8430 also, it's very similar, just less devices and paths). I have t
o
share devices with MVS so we had ESCON directors so the paths could be
shared between VM and MVS, (running on separate boxes), that's what the
As Robert Nix mentioned, the easiest and safest way to get the system nod
e
name is to use the CP QUERY USERID command. No dependencies on SYSTEM
NETID or IPLPARMS and it's a class G command, (anybody can use it). I us
e
it in lots of Execs to determine what system I am on. In a REXX Exec,
IBMLINK 2000 reminds me of Conan O'Brien's running gag on the Late Show
about looking into the future...all the way to the year 2000! :-)
Maybe it's time for an IBMLINK Vista version! Whoops I didn't say that,
did I! Happy Friday!
Dale R. Smith
Technology Services Senior
IBM Global
Most CMS MODULEs are variable length instead of fixed length. Since XEDI
T
strips trailing blanks from variable length records when the file is save
d
or filed, it can cause future executions of the MODULE to fail if some of
those trailing blanks were used by the MODULE. This can happen if
Phil, if you are using a more recent level of LE, they changed the defaul
t
for ALL31 from OFF to ON. With ALL31 set to ON, LE assumes that all the
code invoking LE is running in 31-bit mode. If any part of POPPER is
running in 24-bit mode then this could cause a problem. We have a lot of
