When using MAILTOOL (whether with MAILTOOL or SPL2EMAIL) turning on debugging is as easy as specifying DEBUG(*YES) on the MAILTOOL or SPL2EMAIL command. 

Once the command completes, there should be a trace file (and possible other files) in the IFS that can assist with debugging.  If you're using MAILTOOL Plus and up to date on versions the files may already be there.

Choose the method you're using below, either MAILTOOL Plus, G4MS (Office 365) or G4G (GMail), to determine which debug and trace files to send.

MAILTOOL Plus - Using SENDWITH(*MAILTOOL):

The file you will want to either examine, or forward to us for help, is the following:

/tmp/mailtoolsmtp_xxxx.txt

Where xxxx is a sequential and unique email ID.  If you are up to date on MAILTOOL versions this ID should be in the job log.   

Example:

Error sending email.  Error sending email. ID:155294

If you don't see this in your job log because your version is a little older, you can check data area MLT001DA for the ID of the last email sent:

Command:

DSPDTAARA DTAARA(MLT001DA)

Result:   

Data area . . . . . . . :   MLT001DA         
  Library . . . . . . . :     MAILTOOL     
Type  . . . . . . . . . :   *DEC             
Length  . . . . . . . . :   13 0             
Text  . . . . . . . . . :   MAILTOOL         
Value . . . . . . . . . :   155300  <------------ This should be the ID of the last email sent         

If you are on an even older version of MAILTOOL then the file will simply be named /tmp/mailtoolsmtp.txt (and you should think about downloading and updating to the latest version(s) of any software of ours you have installed.  It's free or any licensed partition!).

G4MS - Using SENDWITH(*G4MSMAIL):

This will create files in the IFS with this naming convention:

/tmp/g4ms_xxxx_yyyyyy

Where xxxx again is a sequential and unique ID for the email.

Again, the ID should be in the job log. 

Example:

Creating email with ID 270040. 

If you happen to be on an older version and this doesn't appear in the job log, check the value of data area G4MSFID:

Command:

DSPDTAARA DTAARA(G4MSFID)

Result:   

Data area . . . . . . . :   G4MSFID                     
  Library . . . . . . . :     G4MSBVS                   
Type  . . . . . . . . . :   *DEC                        
Length  . . . . . . . . :   24 0                        
Text  . . . . . . . . . :   G4MS - Unique ID            
Value . . . . . . . . . :   270042  <------------ This should be the ID of the last email sent                    

G4G - Using SENDWITH(*G4GSMAIL):

This will create files in the IFS with this naming convention:

/tmp/g4g_xxxx_yyyyyy

Where xxxx again is a sequential and unique ID for the email.  You can find the ID if you are on version v16.00 SP260222 or higher in the job log:

G4G Message ID: 506225. 

If you aren't up to date on versions, you can check the value of data area G4GFID to get the last used ID, or at least close to it, so when you look in the /tmp directory you should be able to find the files require:

Command:

DSPDTAARA DTAARA(G4GFID)

Result:

Data area . . . . . . . :   G4GFID                      
  Library . . . . . . . :     G4GBVS                    
Type  . . . . . . . . . :   *DEC                        
Length  . . . . . . . . :   24 0                        
Text  . . . . . . . . . :   G4G - Unique ID             
Value . . . . . . . . . :   505897 <------------- This should be the ID of the last email sent with G4G                     

Send Us the Files AND the Job Log

If possible, please also send a job log in text or PDF format.  

And finally, please send the version of MAILTOOL.  That can be found using this command:

DSPDTAARA DTAARA(MAILTOOL/MAILTOOLV)

If you're using G4MS also send us the G4MS version:

DSPDTAARA DTAARA(G4MS/G4MSV)

If you are using G4G also send us the G4G version:

DSPDTAARA DTAARA(G4G/G4GV)

Contact us with any questions.