How to SEND an AS/400 Save File via Email

WARNING:- 23 Feb 2006 - This document was originally written for internal use by ActionWare Development and Support staff . Most of the information herein is OBSOLETE. Use of this document is NOT recommended.

INTRODUCTION

These instructions have been written for internal use by ActionWare400 development personnel. However by reading between the lines they can be used more generically in a different environment to prepare and send a file containing one or more AS/400 objects. This file can then be sent as an email attachment, or via FTP.

These instructions use two different AS/400's, note that using one AS/400 works just as well. It just so happens that using two was more compatible with the environment at ActionWare.

IN the instructions which follow, you will need to substitute some of the names used with your equivalent name. Here is a list of the ActionWare specific names and what they represent:

APP21 is the name of the ActionWare400 development AS/400.
APPINTEC is the name of another AS/400 which has a drive mapped as letter J:
JCONFIG is the name of the folder to which the J: drive is mapped.
CHGMOO and CHGAPA are AS/400 commands which perform the functions described.
UTEMP is the name of a temporary work library.
V3R2M0 is the oldest version of OS/400 supported by ActionWare400.

 

START HERE

On the development AS/400 (APP21), create a temporary library named AWTEMP and compile or copy the objects for distribution to it.
IMPORTANT- Ensure the objects are created with a Target Release of V3R2M0.

Run command CHGMOO QDFTOWN AWTEMP to change ownership of all objects and the library itself to QDFTOWN.

Run command CHGAPA AWTEMP to change public authority of all objects to *ALL.

Create the save file on APP21 in library UTEMP named AWTEMP
CRTSAVF UTEMP/AWTEMP AUT(*ALL)

Save the contents of library AWTEMP into the save file.
SAVLIB AWTEMP *SAVF SAVF(UTEMP/AWTEMP) DTACPR(*YES) TGTRLS(V3R2M0)

Do this on the PC, forget the rest (2/23/2006)

ftp app44
(user id and password)
binary
dir (required because of exit program)
cd /
get /qsys.lib/utemp.lib/awtemp.file c:\awtemp.savf
quit


FTP the save file to the root of the J: drive on APPINTEC, name it AWTEMP
(Note- this can be any drive addressable from APP21, it does not have to be on a different AS/400)

From a 5250 session command line on APP21 ....

FTP APPINTEC
When requested, sign on with your user id and password, then ....

cd /
binary
put utemp/awtemp /qdls/jconfig/awtemp
quit

The file is now ready to be sent. It can be sent from a PC Email client such as Outlook Express as a file attachment (preferred method), or it can be sent directly from the AS/400.

 

 

SENDING THE FILE FROM A PC EMAIL PROGRAM

This is the preferred method.

The PC file created above needs to be accessible at the PC you are going to use to send the email. If the AS/400 folder where you stored it is mapped to that PC, then the file is directly accessible. Otherwise use some other method to get the file to the email PC. A floppy diskette is usually the easist method.

Launch the email program, open a new message, type a short note to the recipient, and attach the file in the normal manner.

Address the email and click Send.

Congratulations! You have finished the task. You can go home now!!!

 

SENDING THE FILE DIRECTLY FROM THE AS/400

This section assumes the AS/400 is configured for this function and has access to the internet.

On an APPINTEC session, use command WRKFLR, navigate to folder JCONFIG, locate file AWTEMP, use option 8 to change the text (this becomes the subject of the email), then use option 10 to send the file via email. You have the option of using F9 to add key a short message to the recipient.

Assuming the recipient is using a PC email client, such as Eudora, or Netscape, or Outlook Express, the short message will be received as the email, and the file AWTEMP will be an attachment to the email.