|
Thanks Gary
I have exit programs for FTP and is working fine.My concern is about simple file transfer and the exit point is QIBM_QTF_QTRANSFER and the Exit point format is TRAN0100.I am searching hard for documents about the parameters list for this exit point format(TRAN0100) and also samples for this Exit Point.I wrote a small exit program but I am not sure it's working.
Can I use the same paramer list for which I use FTP Client/Server Exit Programs ie VLRQ0100.Are both the same?.
Highly appreciating your help.
Rizwan Ahamed
Programmer-analyst / Software developer
rizwan@nscsa.com.sa
NSCSA.
Telephone : (966) 4785454-611
Fax : (966) 4778036
Site internet / Website : www.nscsa.com.sa
E-mail : itdmail@nscsa.com.sa
-----Original Message-----
From: Gary R. Patterson [SMTP:midrange-l@nexsource.com]
Sent: Tuesday, August 29, 2000 8:18 AM
To: MIDRANGE-L@midrange.com
Subject: RE:
You can debug programs running in an FTP server job. Remember to compile
your ILE program with DBGVIEW(*SOURCE).
1) Start an FTP session and supply a valid user ID and password.
C:\WINDOWS>ftp MY400
Connected to MY400.
220-QTCP at MY400.
220 Connection will close if idle more than 166 minutes.
User (MY400:(none)): MYPROFILE
331 Enter password.
Password: xxxxxxxxxx
230 MYPROFILE logged on.
2) In a terminal session, identify the server job that you are connected to
(it will hold a lock on the user profile used to log into the FTP server):
WRKOBJLCK MYPROFILE *USRPRF
Note: If you sign on to FTP using a profile that is widely used, you might
see a lot of jobs locking that profile. An easy way to determine which one
is yours is to enter the DSPJOB command as an FTP remote command (in the FTP
client window):
ftp> quote rcmd dspjob
Check WRKSPLF for the FTP signon profile and find the job name in the
QPDSPJOB spooled file.
3) Start a service job over the job identified in step 2.
STRSRVJOB QTPFTPxxxx
4) Start debug. Since you are servicing another job, debug commands apply
to the serviced job.
STRDBG MYLIB/MYPROGRAM UPDPROD(*YES) DSPMODSRC(*YES)
5) Set breakpoints, or step.
BREAK xx -OR- F10
6) Cause the program to be invoked (I am just doing an explicit FTP remote
command invocation. You can execute any AS/400 command in FTP by executing
"QUOTE RCMD command". If you are using an FTP exit program, just do a
download (or whatever) to kick off the exit program.
ftp> quote rcmd CALL MYLIB/MYPROGRAM
7) The source debug screen will pop if and when your program hits your
breakpoint(s). Since you are servicing another job, it will be slower than
debugging in the same job. You can use manual debugging if you prefer, but
it is slow, too.
(I'm on OS/400 V4R4, and I used the Win98 FTP client to connect to the
AS/400 FTP server. Sample program was an ILE RPG program compiled with
DBGVIEW(*SOURCE).)
Gary R. Patterson
NexSource, Inc.
980 N Michigan Ave, Suite 1400
Chicago, IL 60611
(312) 214-3526
640 W. Main St.
Louisville, KY 40202
(502) 581-0106
Information technology services for business
http://www.nexsource.com
-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Pete Hall
Sent: Monday, August 28, 2000 8:59 PM
To: MIDRANGE-L@midrange.com
Subject: Re:
At 04:03 08/27/2000 , Rizwan Ahamed wrote:
>Any ways to debug an file transfer exit program(ie like downloading &
>uploading files from and to AS/400 eg thru Client Acess and not FTP).I
>found 5 jobs I remember in wrkactjob during file transfer and how to use
>StrSrvJob for that?.Any ways to debug apart from strsrvjob like submitting
>to job?.Would appreciate any help.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.