Dezhi Systems support site

When doing an XMIT of a data set to an output data set, the XMIT "FROM" node in the resulting XMIT file will be set to "NODENAME" whereas a call to SYSVAR(sysnode) returns "N1". Not a big deal, but it does play havoc with routines that expect both to be the same. If you can do something about this, I'd be grateful.

When transmit a MVS file to a XMIT format dataset, we can issue following TSO command:

Code: Select all

XMIT N1.userid DATASET('source.dataset') OUTDSN('target.dataset.XMIT')

This way, the output dataset will be created by XMIT.

sysprog wrote:When transmit a MVS file to a XMIT format dataset, we can issue following TSO command:

Code: Select all

XMIT N1.userid DATASET('source.dataset') OUTDSN('target.dataset.XMIT')

This way, the output dataset will be created by XMIT.

I know the syntax of the XMIT command, and, FWIW, N1.userid can be replaced by TO.prino when XMITting data to an output dataset. The "problem" is that the INMR01 record does not contain the correct "FROM" node, but "NODENAME", which plays havoc with tools that expect it to be the same as "SYSVAR(sysnode)", in this case "N1"

The following is an actual INMR01 record from a dataset I created yesterday, with unprintables replaved by '.':

Code: Select all

.\INMR01......&......NODENAME......PRINO......TO......PRINO......20090816140709.......

and I would have expected "NODENAME" to be "N1".