ESP Workload Automation

  • 1.  FTP Space For Mainframe File In An Upload

    Posted Aug 28, 2018 08:46 AM

    Last night we had an ESP FTP upload job fail with a 451 error:

    Uploaded 13619358 bytes in 8.783 seconds, 1514.30 Kbytes/sec.    
    451:Transfer aborted due to file error.  

     

    The Programmer did not know what this meant or how to resolve it.  Turns out the file did not have enough space.  My questions are:

    1.  By looking at the uploaded bytes and receiving the 451 message - would that be an indication that there was a space problem?  For the future, would this be what should be looked at?

    2.  Some of our ESP FTP jobs pre-allocate the Remotename (mainframe) file outside of ESP.  Is there a certain amount of space that should be used when doing this?

    3.  Some of our ESP FTP jobs do not pre-allocate the Remotename (mainframe) file outside of ESP.  They use the SITE CMD for Lrecl and DCB.  Do they also need to include a space parameter?

    4.  Is there a default to the amount of space ESP provides a mainframe file if a space parm is not provided?     

    5.  Is there anything we can code that would eliminate this error in the future?                    



  • 2.  Re: FTP Space For Mainframe File In An Upload
    Best Answer

    Posted Aug 28, 2018 12:23 PM

    Hi,

    For a starter on this discussion. 

     

    See the responses below.......Was this transfer done in a piece of JCL or did it use an agent? 

    Depending on the answer to the above question determines the answers slightly. 

    In either case, ESP is not involved in the FTP.  When an agent is used the Java FTP program in the agent is used. 

     

    1) Normally as part of the 451 message or the next message it will say whether it is a space issue. If you would like send all the messages from the FTP.  Usually for a space issue there will be something like an SB37 message.  

     

    2) Make sure the space that is allocated is sufficient for the file that is going to be transferred into it. This varies widely depending on the dataset. Someone will ding me on my following statement. Space is relatively cheap these days. It is best to overallocate it. This will cover it for files that vary from day to day. 

     

    3) Space can be included as part of the FTP SITE commands.  

     

    4) I do not know how much space the system gives by default to an FTP.   

     

    5) There is not an absolute method that will guarantee enough space on the mainframe. 

     



  • 3.  Re: FTP Space For Mainframe File In An Upload

    Posted Aug 28, 2018 01:03 PM

    Thanks for you response!

    The FTP is done through an agent.

    I didn't find any type of space statement in the spool.  Here is what I have:

     

    230 _EPS_P is logged on.  Working directory is "TSOCLX.".     

    SYST                                                                   
    215 MVS is the operating system of this server. FTP Server is running on
    Uploading ASCII D:\\EPS_SYSTEMS\\EXTRACTS\\EPS_GNRL_EPGNRLEX1_EP005CBL_E
    PBSZ 0                                                                 
    200 Protection buffer size accepted                                    
    PROT P                                                                 
    200 Data connection protection set to private                          
    PASV                                                                   
    227 Entering Passive Mode (10,131,73,200,141,73)                       
    TYPE A                                                                 
    200 Representation type is Ascii NonPrint                              
    STOR 'EAS.EPS.GNRLWSL'                                                 
    125 Storing data set EAS.EPS.GNRLWSL                                   
    Cipher Suite SSL_RSA_WITH_RC4_128_MD5 is used for this connection      
    Uploaded 13619358 bytes in 8.783 seconds, 1514.30 Kbytes/sec.          
    451:Transfer aborted due to file error.                                
    QUIT                                                                   
    221 Quit command received. Goodbye.                                    
    Logged out                                                             



  • 4.  Re: FTP Space For Mainframe File In An Upload

    Posted Aug 28, 2018 03:40 PM

    Hi, 

    There is no definitive space issue in the output. I assume that someone was able to make the z/OS dataset larger and transfer it OK?



  • 5.  Re: FTP Space For Mainframe File In An Upload

    Posted Aug 29, 2018 07:28 AM

    Once it was decided that the issue was related to space – but it took a few hours and several phone calls to determine it.  The JCL pre-allocated space has been increased. I will add this situation to things to look for based on  the ESP message.  Thanks for your time and help – it is appreciated!