The following instructions show you how to set up and use the POPRECVJ command in POP/400 to retrieve POP email messages and attachments and store them in an IFS folder. Message headers are stored in the POPHDR2 file in the library RJSPOP3.
  • V5R1 or above
  • Java JDK version 1.4
  • POP/400 version 1.10 or above
To set up and use POPRECVJ:
  1. Confirm that Java JDK 1.4 is installed by running the following command:

    WRKLNK OBJ('/qibm/ProdData/Java400/jdk14')

    If the jdk14 directory displays in the list, Java JDK version 1.4 is installed. 

  2. Add RJSPOP3 to your library list:


  3. To restore the necessary Java objects for POPRECVJ, run the following command:


  4. To retrieve email messages, run the POPRECVJ command:
    1. Type: POPRECVJ
    2. Press F4.
    3. Fill the following parameters:
      • Pop server host: The host name or IP address of the POP3 server to retrieve mail from.
      • Pop user: A valid POP3 user ID.
      • Pop password:  The password for Pop user.
      • Delete messages after: Whether to delete all messages from the POP mailbox after downloading to the iSeries. Choose *YES or *NO.
      • Dest message text dir: The IFS folder to store the downloaded messages in. 
      • Dest message attachment dir: The IFS folder to store the downloaded attachments in. 
      • Debug mode: Whether to include debug messages in the java log. Choose *YES or *NO.
      • Display standard output result: Whether to display the java log after running the command. Choose *YES or *NO.
      • Delete standard output result: Whether delete the java log temp IFS file after running the command. Choose *YES or *NO.
      • Exit program to process message: If you want a CL exit program to process the messages, the program name.

        Note: A sample exit program source can be found in the file SOURCE in the library RJSPOP3.

        For example: To retrieve messages from a POP3 server with host name, use:


Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case