This page is about the old original file upload program dated year 2003 and named fupload.

Though this program has been outmoded by the Ron Egyed's fupload2 program, I believe that some documentation should be kept, at least for the former users, who may still have it.

The major restriction in this program is that you cannot upload files larger than 16 Mb. Also program customization is rather difficult.

1. Using the FUPLOAD program

• If you installed the Original HTTP directives to run FUPLOAD, enter the following in the location line of your browser:
  http://yourTcpAddr/fuploadp/fupload.pgm
• If you installed the Apache HTTP directives to run FUPLOAD, enter the following in the location line of your browser:
  http://yourTcpAddr:8027/fuploadp/fupload.pgm

Figure 1- FUPLOAD initial screen

• Enter the target IFS file
• Optionally enter some description
• Use the browse button to select from the PC the file to be uploaded
• Press the submit button

The followin screen is then displayed:

Figure 2- FUPLOAD file uploaded

2. Tailoring program FUPLOAD to your needs
You should develop your file upload program in a library of yours (never create objects in library FUPLOAD).
Some experience with ILE-RPG and cgidev2 WEB programming is required.

Open a separate window to display the ILE-RPG source of the upload CGI fupload.

To better understand how the program works

1. set variable DetailSW to a non blank value:

   29.00 D DetailSW s 1a inz('x')

2. recreate the program via command upload/compile

Some comments on program execution.
It goes through the following steps:

1. Retrieves the length of the input buffer. If length is zero, it issues the page asking for input data. If length not zero, it should process the upload request. We shall deal with this case (PART 2).
2. Allocates an amount of storage equal to the length of the input buffer
3. Calls the "standard input" API to receive the input buffer in the allocated storage
4. Converts a maximum of 1,000 initial input ASCII characters to EBCDIC. This is important, as the control parameters are expected in the first 1,000 initial characters (this is why the file to be uploaded was the last input field in the form used to launch the upload request)
5. If requested so by the DetailSW, it displays some data (the first 1,000 chars and the MIME headers falling in this string) in the response HTML page.
6. Retrieves all the parameters which are needed for the upload. This is a very important part, that you must customize any time you need to add or change input parameters. The following parameters are retrieved:
   1. Path and name of the local file ("FileName"). This will just be reported in the HTML response page.
   2. Type of the local file ("FileType"). This will just be reported in the HTML response page.
   3. Start position (in the buffer) of the local file to be uploaded ("StrPos"). This is a vital piece of information.
   4. Size of the local file to be uploaded ("FileSize"). This is a vital piece of information.
   5. Path and name of the server IFS file to be created ("ServerFile"). This is a vital piece of information.
   6. Description ("Description"). This parameter is just provided to teach how to handle parameters added for program customization.
7. Makes sure that the target directory ("ServerDir", the IFS directory where the local file should be uploaded) exists
8. Performs the upload (routine "WrtDta"). This is done through the following steps:
   1. Delete the server file, if already existing
   2. Open the server file for output
   3. Write to the file the string in the input buffer containing the local file to be uploaded
   4. Close the server file
9. Report the outcome of the operation in the response HTML page.