We have a batch job that is failing to send the SMTP email we want it 
to send.  We have a number of other batch jobs that are working just fine in 
this regard.
        Unlike the working jobs, which are submitted by our job-scheduler, this 
one is submitted via a CICS transaction using a TD queue.  The CICS-region's 
authority user-ID has authority through a profile in the SURROGAT class to 
submit the job using the FIDUFLX1 ID (a functional or non-personal ID) that is 
supposed to run the batch job.  The JCL and control cards for the job, as 
submitted, are:

  //SUBUBF1H JOB 021210F00210P,H,CLASS=G,MSGCLASS=U,USER=FIDUFLX1      
  //STEP00  EXEC PGM=IEFBR14                                           
  //DD1      DD DSN=UN.UB.PD.UBCUBF1.MAIL,UNIT=(,,DEFER),              
  //            DISP=(MOD,DELETE,DELETE),SPACE=(CYL,1)                 
  //STEP01  EXEC  PGM=SYNCSORT                                         
  //STEPLIB  DD  DSNAME=SYS1.SORTLIB,DISP=SHR                          
  //SORTIN   DD  *                                                     
       -- in-stream message records to go into the *.UBCUBF1.MAIL --
       -- dataset to indicate the nature of the problem           --
  //SORTOUT  DD  DSNAME=UN.UB.PD.UBCUBF1.MAIL,DISP=(NEW,CATLG,DELETE), 
  //         SPACE=(TRK,(1,1),RLSE),UNIT=DISK,                         
  //         DCB=(RECFM=FB,LRECL=80,BLKSIZE=4080)                      
  //SORTWK01 DD  UNIT=DISK,SPACE=(CYL,(55))                            
  //SYSIN    DD  DSN=U.SCHDP.CNTRL(RUSRFDMP),DISP=SHR        <-- (this is just 
a file copy)
  //SYSOUT   DD  SYSOUT=*                                              
  //SYSPRINT DD  SYSOUT=*                                              
  //STEP02   EXEC PGM=IKJEFT01,DYNAMNBR=20                             
  //SYSPROC  DD DISP=SHR,DSN=SYSTEMS.PROD.SYSEXEC                      
  //SYSTSPRT DD SYSOUT=*                                               
  //SYSTSIN  DD *                                            <-- in-stream 
control cards as follows
     SMTPNOTE BATCH -
   SUBJECT(' ERROR IN PARAGRAPH GET-WAGES (UBF1)             <-- or some other 
subject statement
      ') -      
     DATASET('UN.UB.PD.UBCUBF1.MAIL') -
     TO(fluid...@awi.--rest-of-address--) BATCH
  /*
  /*EOF

        I do note that the control statements have the word 'BATCH' present 
twice, first immediately after the "SMTPNOTE" parameter, and again after the 
email address.  I am not sure if this is connected to the problem or not.
        The job's run-authority ID (FIDUFLX1) has an alias to a user-catalog, 
since our experience has shown that this is needed for at least one dataset 
that SMTP allocates. 

        The results from the 'STEP02' job-step are:
  READY                
     SMTPNOTE BATCH  SUBJECT(' ERROR IN PARAGRAPH GET-WAGES (UBF1)              
        ')        
  DATASET('UN.UB.PD.UBCUBF1.MAIL')   TO(fluid...@awi.--rest-of-address--) BATCH 
  
  EZA5580E UNABLE TO DELETE TEMPORARY DATASET '.SMTPPR.TEMP.TEXT'     
  READY       

        SMTPPR is the name of our mainframe SMTP started task.  Please note 
that the temporary dataset it is attempting to delete is '.SMTPPR.TEMP.TEXT' 
and is lacking a high-level-qualifier, which is the obvious reason why the 
temporary dataset cannot be built or deleted.         
        As far as I can tell, everything for this job's ID is set up the same 
as for the IDs whose (normal) batch jobs are successfully sending SMTP emails.

        Any ideas on what I am overlooking or missing???                        
                                                                                
  

David Mueller | Systems Programmer 
SSRC (Southwood Shared Resource Center) 
4070 Esplanade Way, Room 360D  
Phone: 850-414-9134 || Fax: 850-488-3600 
E-mail: david.muel...@ssrc.myflorida.com 
  
Please Note: Florida has a very broad public records law. Most written 
communications to or from state officials regarding state business are public 
records available to the public and media upon request. Your e-mail 
communications may therefore be subject to public disclosure. 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to