T01F3005E FTP is not authorized to access user information.

Document ID : KB000053118
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

An FTP3 batchjob may appear to fail with an incorrect password or an inability to find the stack. The additional messages differ depending upon whether or not a NETRC file is used.

Solution:

An FTP batchjob may fail with these messages if a NETRC file is used

T01F3000I ProductID: Unicenter TCPaccess Communications Server Rel 6.0.0
T01F3000I (C) Copyright 1987-2003 Computer Associates International, Inc.
T01F3000I Component: Client FTP, A6007524 T01PFMN
T01F3005E FTP IS NOT AUTHORIZED TO ACCESS USER INFORMATION.
T01F3018E TCPIP subsystem is not currently available

If no NETRC file is used and the login information is located in the //INPUT DD *, the FTP3 batchjob will fail with

T01F3000I ProductID: Unicenter TCPaccess Communications Server Rel 6.0.0
T01F3000I (C) Copyright 1987-2003 Computer Associates International, Inc.
T01F3000I Component: Client FTP, A6007524 T01PFMN
T01F3005E FTP IS NOT AUTHORIZED TO ACCESS USER INFORMATION.
T01F3354I 530-TSS7100E 009 J=SNSWILMA A=THOLO01 T=N/A F=VMAN - Incorrect Password
T01F3354I 530 TSS7101E Password is Incorrect
T01F3017E Unable to log in to the local host: FTP Return Code = 26530.
T01F3310I FTP Return Code = 26530.

In both instances the key message is the T01F3005E and the actual problem is the same.

There are two possible causes.

  1. All libraries defined in the STEPLIB of the job must be APF authorized. If this was not done, or the APF authorization is incorrect in some manner, the job will fail.

  2. If the job is running on a system where multiple LPARs are sharing JES, system affinity must be defined so that the job runs on the correct system. Depending on your system, you may need to add this directly after the jobcard:
    /*JOBPARM SYSAFF=xxxx
    where xxxx is the four alphanumeric character system ID of one of the JES2 systems
    in your installation's multi-access spool configuration.

Please see the IBM JCL manual if further clarification is required.