EQQJ509E - TABLE GLOBAL NOT FOUND

TSO Programming, ISPF, SDF, SDSF and PDF, FTP, TCP/IP Concepts, SNA & SNA/IP etc...
Papya013
Posts: 35
Joined: Wed Nov 06, 2013 6:53 pm
Skillset: COBOL JCL DB2
Referer: Friend

EQQJ509E - TABLE GLOBAL NOT FOUND

Postby Papya013 » Thu Mar 28, 2019 12:46 pm

Hi Team,

I am trying to send a file to a FTP server through JCL as mentioned below. I am getting an error "EQQJ509E - TABLE GLOBAL NOT FOUND".

Code: Select all

//FTP1     EXEC PGM=FTP,PARM='(EXIT TRANSLATE ISO'  
//*%OPC SCAN                                        
//SYSPRINT DD  SYSOUT=*                            
//OUTPUT   DD  SYSOUT=*                            
//INPUT    DD  *                                    
11.22.33.44                                        
abcd                                          
xxx?xxxxx                                          
CD file                                      
PUT 'A.B(0)' R130B_&OYMD1..txt                
QUIT                                                
/*  



I tried to search in forums for this issue and could understand that some libraries have to be included. I am not sure if its because of the special character ( ? ) used in the password.


Could you please help me out here.


Regards,
Balesh GG

NicC
Global moderator
Posts: 3025
Joined: Sun Jul 04, 2010 12:13 am
Skillset: JCL, PL/1, Rexx, Utilities and to a lesser extent (i.e. I have programmed using them) COBOL,DB2,IMS
Referer: Google
Location: Pushing up the daisies (almost)

Re: EQQJ509E - TABLE GLOBAL NOT FOUND

Postby NicC » Thu Mar 28, 2019 4:24 pm

What does your TWS support say?
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic

Blackthorn
Posts: 130
Joined: Tue Feb 01, 2011 7:12 pm
Skillset: JCL, TWS, IBM Utilities
Referer: Found on web

Re: EQQJ509E - TABLE GLOBAL NOT FOUND

Postby Blackthorn » Tue Apr 02, 2019 5:02 pm

Yes, as well as the more usual & variables, there are also ? and % variables in TWS with special meanings. Thus it is trying to resolve the ?xxxxxx variable. Normally the solution would be to move the //*%OPC SCAN statement after this, so that it will not attempt to resolve that variable. But I guess having that statement in your FTP parameters may cause other issues.

The obvious question is do you need that ? in the password field or can you change that? The only other thing I can think of is to point to a specific variable table where the variable ?xxxxx is resolved with a value of ?xxxxx. A bit messy, but it would perhaps achieve the desired result.


  • Similar Topics
    Replies
    Views
    Last post