08-30-2008
any body has any information about NDM
Hi All,
Any kind of literature related to NDM or its processes/syntax will be of great help.
At least it would be appreciated if anybody can tell me if we can use NDM without hardcoding the user/pwd.
for example,
snodeid=(${LOGIN})
or,
snodeid=(`cat ${PDIR}/ndm.pwf`)
Kindly reply if you have any idea regarding NDM.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
..................................
Network data mover is a secure mechanism to transfer data .
can any body guide me out ....
how it is done (1 Reply)
Discussion started by: anumkoshy
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have configured NDM (Connect: Direct) to copy a bunch of files from one server to another. I create a master file contains the list of files which need to copied, and my shell script read the file and send the file one by one thru NDM. The problem is, since the files are very big in size... (0 Replies)
Discussion started by: r_sethu
0 Replies
3. Shell Programming and Scripting
I have an ASCII file that I receive on a monthly bases that is fixed length. I break the file into separate files based on a 5 character numerical sequence. I have 20 different sequences I have to find.
the input file looks something like this
xy-ins 2008yuthnrlsinrthsntwilgrha33260001... (4 Replies)
Discussion started by: jcalisi
4 Replies
4. Shell Programming and Scripting
I'm sure it's really easy, but I have searched on Google and on the forums and haven't found anything.
For instance, if I open the grep manual (man grep), I can't close it.
I've tried ctrl+c, ctrl+x, scrolling to the bottom of the manual.
How can I exit the manual without closing the shell?
... (8 Replies)
Discussion started by: dennis89
8 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder?
Source file open failed. Error= 2
Regards,
Balamurgan (1 Reply)
Discussion started by: krbala1985
1 Replies
6. Shell Programming and Scripting
I am using ndmcli to NDM my files. When i do so it prints success for the process, with out any errors, but file is not reached at destination.
ndmcli -x << EOJ
submit phcdb process snode=$RMT_NODE_NAME
step01 copy from (file=$SRC_FILE_NAME pnode)
to (file=$DST_FILE_NAME
snode... (0 Replies)
Discussion started by: pattamuthu
0 Replies
7. Shell Programming and Scripting
Hi All,
I have a requirement where i need to NDM 3 files from LINUX to Mainframe system & trigger a job in mainframe once the 3 files are transmitted successfully.
I am getting an error message in the && operator (the code component where i am checking whether step 1/2/3 are completed).
... (2 Replies)
Discussion started by: dsfreddie
2 Replies
8. Shell Programming and Scripting
Hi,
I am using ndmcli to send files from one solaris server to another one.
I use the below one in script and verify the status.
select stat det=yes pnum="$PNUM"
Is there any option to automate in script in verifying destination size with source after doing NDM? :mad: (10 Replies)
Discussion started by: gthangav
10 Replies
9. Shell Programming and Scripting
Friends,
I am trying to use the below type of code in my script, but its not at all executing, its an ndm scripting called inside the shell script,
Any help is greatly appreciated,
vsource=/temp/ndm
vtarget=/temp/ndm
vlist=list.txt
for i in $( cat $dir/$file1 )
do
v1=$i
... (1 Reply)
Discussion started by: aa_remo
1 Replies
10. Homework & Coursework Questions
Hi Experts,
I am trying to run a Mainframe Job from Linux using NDM process.
I will be passing the contents of the Mainframe job as an parameter to the NDM script. This is working fine with FTP when i use the option filetype = jes, but in NDM i am not able to identify a similar option like... (2 Replies)
Discussion started by: arun1377
2 Replies
MAN(1) General Commands Manual MAN(1)
NAME
man - print out the manual
SYNOPSIS
man [ - ] [ -a ] [ -M path ] [ section ] title ...
DESCRIPTION
Man is the program which provides on-line access to the UNIX manual. If a section specifier is given, man looks in that section of the
manual for the given title(s). Section is either an Arabic section number (``3'' for example), or one of the words ``local'', ``new,'' or
``old''. (The abbreviations ``l'', ``n'', and ``o'' are also allowed.) If section is omitted, man searches all sections of the manual,
giving preference to commands over library subroutines, and displays the first manual page it finds, if any. If the -a option is supplied,
man displays all applicable manual pages.
Normally man checks in standard locations (/usr/man and /usr/local/man) for manual information. This can be changed by supplying a search
path (a la the Bourne shell) with the -M flag. The search path is a colon (``:'') separated list of directories in which man expects to
find the standard manual subdirectories. This search path can also be set with the environmental variable MANPATH.
Since some manual pages are intended for use only on certain machines, man only searches those directories applicable to the current
machine. Man's determination of the current machine type can be overridden by setting the environmental variable MACHINE.
If the standard output is a teletype, and the - flag is not provided, man uses more(1), or the pager provided by the environmental variable
PAGER, to display the manual page.
The FORTRAN version of section 3 of the manual may be specified by supplying man with the section ``3f''. Also, a specific section of the
local manual may be specified by appending a number to the section, i.e. ``l5'' would indicate section 5 of the local manual.
FILES
/usr/man standard manual area
/usr/man/cat?/* directories containing standard manual pages
/usr/local/man/cat?/* directories containing local manual pages
/usr/src/man directories containing unformatted manual pages
SEE ALSO
apropos(1), more(1), whatis(1), whereis(1)
BUGS
The manual is supposed to be reproducible either on the phototypesetter or on a typewriter, however, on a typewriter, some information is
necessarily lost.
4th Berkeley Distribution April 19, 1988 MAN(1)