short.text=CMGR RPC call returns NULL
long.text=The ndmapi_sendcmd RPC call made by the API to the CMGR returns a
NULL pointer.There is probably an RPC error.ndm.action=None
user.action=First, check if the ndmcmgr is still running; it could have
been killed accidently.If so, then abort the current CLI and restart the
CLI. If the same problem occurs again, try to increase the value of wait
time (if set) in the API configuration file (ndmapi.cfg).
Precompressing/Decompressing Files Using the Standalone BatchCompression Utility
The Standalone Batch Compression Utility (cdsacomp) enables you to precompress
files and then transfer the precompressed files to remote Sterling Connect:Direct
nodes using Sterling Connect:Direct Processes. Youhave the following options for
decompressing the files. A file can either be:
vDecompressed as it is received by the remote node (available on all Sterling
Connect:Direct platforms)
vStored on the remote node and later decompressed offline using cdsacomp
(available only on Sterling Connect:Direct and Sterling Connect:Direct for z/OS).
Because cdsacomp can be used offline, it allows you to allocate some of the
overhead associated with compression to non-peak times. For example, if you need
to send the same file to several remote nodes, use this utility so that the file is
precompressed only one time. Youcan also use cdsacomp to determine how much
compression can be achieved for a file without having to transmit the file.
The cdsacomp utility is located in the Sterling Connect:Direct /bin directory.
Special Considerations for Using the Standalone BatchCompression Utility
Consider the following when you are using cdsacomp to precompress files:
vIf you precompress a file with the cdsacomp utility,then you cannot specify any
compression options in your Sterling Connect:Direct Process when you copy that
file.
vYou cannot specify data transformations (xlate, codepage, strip blanks, and so
on) when sending a precompressed file with :precompress=yes: sysopts (for
on-the-fly decompression). The following transformation options are available:
–-x
–-p
–-s
–-a
vIf you precompress a file with the cdsacomp utility on a Sterling Connect:Direct
node, then you cannot specify a checkpoint interval in your Sterling
Connect:Direct Process if you decompress the file as it is received by the remote
node.
vWhen you are copying a precompressed file to z/OS without :precomp=yes: (for
deferred decompression):
– The Copy operation must specify DCB information for the destination file.
The physical block size of the destination file on Sterling Connect:Direct for
z/OS must match the logical block size of the precompressed source file on
Sterling Connect:Direct for UNIX.
– The logical block size of the source file defaults to 27920 unless overridden by
the -b parameter.
48 Sterling Connect:Direct for UNIX: User Guide