Sponsored Content
Full Discussion: FTP from AIX to Mainframe
Top Forums Shell Programming and Scripting FTP from AIX to Mainframe Post 303010665 by rbatte1 on Friday 5th of January 2018 04:25:03 AM
Old 01-05-2018
You would have to use a checksum algorithm that is the same on both hosts, and I don't know what that would be for MVS. Choosing one that doesn't match may leave you thinking every transfer has failed.

If you can work it out, you may be able to use ftp sub-sommands to run a job on the MVS server on completion of the transfer. If you open up the connection and then type rhelp you will get the commands available and can explore them, e.g rhelp site but I can't remember what it was. Sadly it might have been an AS400 that we used to submit jobs on, so I might be going the wrong way.

Other options, depended on what is supported:-
  • Use SFTP which confirms accurate delivery (or not)
  • Use SSH or remote shell to submit your checksum batch job
  • Pull the files back again (to a separate location) and compare. Of course if the files are large this might not be acceptable in time and space.



I hope that some of this is useful,
Robin

Last edited by rbatte1; 01-05-2018 at 05:28 AM.. Reason: Took out IBM ref. doc.
This User Gave Thanks to rbatte1 For This Post:
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

mainframe FTP error

Hi when i am trying to ftp to a newly cretaed mainframe GDG for the first time,i am getting the following error... Verbose mode on. 200 Representation type is Ebcdic NonPrint 200 Port request OK. 550-SVC99 Return code=4 S99INFO=0 S99ERROR=38668 HEX=970C S99ERSN code X'00004379'). 550... (1 Reply)
Discussion started by: sam99
1 Replies

2. HP-UX

ftp from unix to mainframe

hi suppose i have a file named xyz(-1) and i have to transfer(ftp) it on a Mainframe from unix,how should i do it as whenever i try to do so it says use MVS naming conventions (1 Reply)
Discussion started by: ashishabhishek
1 Replies

3. UNIX and Linux Applications

ftp from unix to Mainframe

suppose i have a file named xyz(-1) and i have to transfer(ftp) it on a Mainframe from unix,how should i do it as whenever i try to do so it says use MVS naming conventions (1 Reply)
Discussion started by: ashishabhishek
1 Replies

4. UNIX for Advanced & Expert Users

ftp file from unix to mainframe

thanks (2 Replies)
Discussion started by: ashishabhishek
2 Replies

5. UNIX for Dummies Questions & Answers

FTP'ing EBCDIC Characters from Mainframe

Hi All, I am new to this site, I have a requirement where in i have to FTP a file from mainframe to Unix box. The catch here is there are few Spanish characters like N with tilde(~) and a with ` etc., all other characters are coming fine but those mentioned above are not coming in a proper... (1 Reply)
Discussion started by: harikiranr
1 Replies

6. Shell Programming and Scripting

FTP files to target Mainframe system

Hi Experts... Greetings for the day..! I just want to FTP the files to mainframe system.. my code is not working..and also i need to put the files in a particular directory in a specific naming format... ftp -i -n ${HOST_NAME} << END_FTP user ${USER_NAME} ${PASSWORD} put ${FILE_NAME}... (3 Replies)
Discussion started by: spkandy
3 Replies

7. AIX

Problems with SSH/SFTP between AIX and Mainframe

Hi, I'm not sure if this has been solved in this forum already but please do help me out if possible. Basically, I've already setup a passwordless SSH connection between 2 AIX IDs (say ID-1 and ID-2) with a Mainframe server ID (say MVSID). I'm able to successfully do an SSH from the AIX server to... (1 Reply)
Discussion started by: sambeet
1 Replies

8. UNIX for Advanced & Expert Users

FTP issues between mainframe and UNIX

Hi All, The issue is that, we have a dataset in mianframe whose record length is 153 characters. And a batch job ftpies it to the unix server(SunOS) as a test file. But the ftpied file in unix does not have a record length of 153 chars. Each record of 153 chars gets splited into two line of... (8 Replies)
Discussion started by: hareeshkumaru
8 Replies

9. AIX

ODBC Connectivity between Oracle10g on AIX and Mainframe

Hi, I have a task of setting up connectivity between Oracle 10g (AIX) and Mainframe (1 library). Went through couple of documents, forums, blogs etc. MY understanding is ODBC Generic Connectivity is free from Oracle side. Question: (may be dumb to you) 1. Has anybody done this and would... (3 Replies)
Discussion started by: jvmani_1
3 Replies

10. AIX

AIX Forum: FTP from AIX to Mainframe

This discussion thread is an extension to what was discussed in Shell scripting section. Please refer the post for the requirement: Requirement Post - Click Here The whole thread - Click Here I would like to know how I can use NDM to transfer file from AIX to Mainframe and to verify the... (3 Replies)
Discussion started by: TechGyaann
3 Replies
CONDOR_QSUB(1)							   User Commands						    CONDOR_QSUB(1)

NAME
condor_qsub - minimalistic qsub emulation for Condor SYNOPSIS
condor_qsub [OPTIONS] [<command> [<command_args>]] DESCRIPTION
Minimalistic emulation of SGE's qsub for Condor. The primary purpose of this emulation is to allow SGE-style submission of dependent jobs without the need to specify the full dependency graph at submission time. This implementation is neither as efficient as Condor's DAGMan, nor as functional as SGE's qsub/qalter. It merely serves as a minimal adaptor to be able to use software original written to interact with SGE in a Condor pool. In general condor_qsub behaves just like qsub. However, only a fraction of the original functionality is available. The following list of options only describes the differences in the behavior of SGE's qsub and this emulation. Qsub options not listed here are not supported. OPTIONS
-b <y|n> If 'y', command and arguments given on the command line are wrapped into a shell script which is then submitted to Condor. --condor-keep-files This is a non-SGE option. If given, it will prevent condor_qsub from deleting temporary files (generated submit files, sentinel jobs). This is mostly useful for debugging. -cwd If given, this option will cause the 'initialdir' value in the Condor submit file to be set to the current directory. -e <filename|path> Name of the file to contain the STDERR output of the job. By default this will be job_name.ejob_id[.task_id]. If an existing direc- tory is specified, the file will be placed inside this directory using the default schema for the filename. -h,--help Print usage summary and option list. -hold_jid <jid> If given, the job will be submitted in 'hold' state. Along with the actual job a 'sentinel' job will be submitted to Condor's local universe. This sentinel watches the specified job and releases the submitted job whenever the job has completed. The sentinel observes SGE's behavior to detect job exiting with code 100 and not start depedent job in this case. If a cluster id of an array job is given the dependent job will only be released after all individual jobs of a cluster have completed. -l <ressource spec> This option is currently ignored. -m <a|e|n><...> SGE's notification labels will be translated (approximately) into Condor's notifications states (Never, Error, Complete). -M <email> Added as 'notify_user' to the submit file. -N <jobname> Determines the default name of logfile (stdout, stderr). -o <filename|path> See -e option, but for a job's stdout. -p <int> Added a 'priority' to the submit file. -r <y|n> This option is currently ignored. -S <shell> Path to a shell binary for script execution. -shell <y|n> This option is currently ignored. -t <start>[-<stop>[:<step>]] Task ID specification for array job submissions. -q <queue name> This option is permanently ignored, as Condor doesn't have multiple queues. -V If given, 'getenv = True' is added to the submit file. --version Print version information and exit. This script is released under the Apache V2.0 License. It was written by Michael Hanke <michael.hanke@gmail.com>. condor_qsub 0.1 September 2012 CONDOR_QSUB(1)
All times are GMT -4. The time now is 02:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy