Back to Blog
Ibm ftp disk controller 7.77.385/19/2023 ![]() I have alway suggested to initiate the file transfers from the workstation,Īnd trigger the appropriate jobs with the file trigger. Usually the workstation powered off, or the ftp service not running The recovery actions in case of troubles, Strongly agree, I have always discouraged mainframe initiated tasks to workstations. Which also eliminated any production job problems caused by connection problems You might check with the prople responsible for the remote system and make sure you have the proper permissions for the path/file you are trying to wrtie to. ![]() Which also eliminated any production job problems caused by connection problems to remote servers (which will happen when there are several hundred "remotes" participating ) Probably comes from more than 15 years of moving files back&forth between win-based, unix, mainframe systems and never running batch ftp on the mainframe.Īll of the distributed requirements were handled by the remote system "pushing to" or "pulling from" the mainframe. I wasn't sure if it was ok or not - just that it was something i was not familiar with. Yup, the DDNAME option looks quite interesting. JCL FTP looks quite a bit more interesting and useful now. I was in maintenance mode at the time, "change this job to send this file instead". I stopped reading after the put/mput chapter and I missed the info I guess many of us started looking starting from the chapter regarding the I did it and the info was right there even if in a place not easy to find Maybe I was sleeping because never occurred to me to search the docs for I had searched for a long time to use the ddname approach. Sometimes the IBM docs are difficult to search. Have you read-up on the concept of writing the results of a list or dir command to a dataset, instead of it going to the OUTPUT DD? It also can be quite handy when needed. Wow, knowing that would have made somethings I had to do about a year ago much easier. The O/P needs to check if it's supported for HIS release of z/OS.Īlso, sendsite should always be supressed unless you're absolutely sure that the remote server can handle it. It's definitely the way to go if you want to use a GDG for the input. Put/ get from/to a DDNAME has been around for a while now. I wonder if your PUT statement is being accepted. Now the JCL is accepting PUT statement if i remove remote file name FTPTEST.TXT Please post the link(s) where you found this. ĮZA1701I > SITE FIXrecfm 133 LRECL=133 RECFM=FBA BLKSIZE=27930ĥ00 'SITE FIXrecfm 133 LRECL=133 RECFM=FBA BLKSIZE=27930': command not understoĮZA1735I Std Return Code = 27550, Error Code = 00002 Now the JCL is accepting PUT statement if i remove remote file name FTPTEST.TXT. ![]() I learnt the Syntax from this forum only. When opening a dataset by dd reference rather than by dsname dd:ddname is the notation used inside a C language program I was going to make the same observation myself The PUT should name a local file and the remote file - not jcl. I am trying to FTP a file to FTP Server, I am getting the following error.ĮZA1735I Std Return Code = 27000, Error Code = 00007 FTP error Return Code = 27000, Error Code = 00007 -IBM MainframesįTP error Return Code = 27000, Error Code = 00007
0 Comments
Read More
Leave a Reply. |