Nice catch, Joe.

Charles,

I would agree about a customer-facing process not generating messages upon 
termination.  However, the FTP daemon isn't "quite" that bad.  Just for 
curiosity, I tried to start a second FTPD on my sandbox.  It did what it was 
supposed to do, started the FTPD1 daemon and shut itself down.  The new daemon 
shut down immediately too.  It didn't say why, but it at least did say it was 
shutting down.  

S FTPD     <<<<< me starting it
$HASP100 FTPD     ON STCINRDR                                          
IEF695I START FTPD     WITH JOBNAME FTPD     IS ASSIGNED TO USER FTPD  
 , GROUP SPTDFGRP                                                      
$HASP373 FTPD     STARTED                                              
IEF403I FTPD - STARTED - TIME=16.56.41                                 
IRR812I PROFILE BPXAS*.* (G) IN THE STARTED CLASS WAS USED 722         
        TO START BPXAS WITH JOBNAME BPXAS.                             
$HASP100 BPXAS    ON STCINRDR                                          
$HASP373 BPXAS    STARTED                                              
IEF403I BPXAS - STARTED - TIME=16.56.41                                
BPXP024I BPXAS INITIATOR STARTED ON BEHALF OF JOB FTPD RUNNING IN ASID 
007D                                                                   
IEF404I FTPD - ENDED - TIME=16.56.41                                   
$HASP395 FTPD     ENDED - RC=0000                                      
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=007D.       
EZY2714I FTP server shutdown in progress                               
EZYFT59I FTP shutdown complete.                                        


Just for giggles, I meandered over into the Unix services syslog.log and found 
this (granted I didn't use a different port for the second daemon):

(snipped for brevity)
ftpdÝ1907¨: EZY2700I Using port FTP control (21)                                
            
ftpdÝ1907¨: EZY2701I Inactivity time is 300                                     
            
ftpdÝ1907¨: EZYFT13E bind error : EDC8115I Address already in use. 
(errno2=0x744C7247)      
ftpdÝ1907¨: EZY2714I FTP server shutdown in progress                            
            
ftpdÝ1907¨: EZYFT59I FTP shutdown complete.                                     
            

So FTPD does indicate what the problem is when it doesn't start up properly.

Rex

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Joe 
Monk
Sent: Monday, July 27, 2020 4:50 PM
To: [email protected]
Subject: [External] Re: Started task stopping immediately. No error messages.

IMHO, the clue to this is in his printout.

PGM=FTPD,REGION=0M,TIME=NOLIMIT,PARM='POSIX(ON) ALL31(ON)/TRACE PORT 990'

IEF043I Actions taken by SMFLIMxx parmlib policy for FTPSD    FTPD
        Step MEMLIMIT set to ONOUDONT by policy - SMFLIM00 0002

So, it looks some exit is killing the task because he has REGION=0M.

The SMFLIMxx policy is killing the task (ONOUDONT).

Joe


On Mon, Jul 27, 2020 at 4:42 PM Charles Mills <[email protected]> wrote:

> Oh man! Talk about user-hostile programming. How could anyone ship a 
> customer-facing program that detects an error and then just quits with 
> (a.)
> RC=0 and (b.) no message whatsoever. No "Hello World I am FTPD V2R3" 
> and no error message. Even if you can't open your usual log or listing 
> file you can WTO 'Unable to open SYSPRINT' (or whatever) or issue a 
> documented ABEND.
>
> Charles
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] 
> On Behalf Of Seymour J Metz
> Sent: Monday, July 27, 2020 8:31 AM
> To: [email protected]
> Subject: Re: Started task stopping immediately. No error messages.
>
> It looks like you're using JES3. I thought thad SDSF didn't support it.
>
> CC 0 would have been a useful datum in the original question. It looks 
> like the FTP server doesn't issue an informational message when a copy 
> is already running. RFE?
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> ________________________________________
> From: IBM Mainframe Discussion List [[email protected]] on 
> behalf of Skippy the Ancient [[email protected]]
> Sent: Monday, July 27, 2020 8:48 AM
> To: [email protected]
> Subject: Re: Started task stopping immediately. No error messages.
>
> Responding to all posters, not just Mr Metz.
>
> 1. I already tried calling the proc from JCL.  It ran, stopped 
> immediately and returned no error messages.
> 2. I started the proc with the MSGCLASS and did receive output.  It 
> was identical to the JCL call; immediate stop and no error messages.  
> I will post this below.
> 3. The started task is a second FTP server supporting FTPS. To 
> simplify, I copied the FTPD proc and renamed it FTPSD.  In theory, it 
> is running exactly as the original FTPD task with a different port. 
> (990) 4. The PROFILE update reads like this - AUTOLOG
>    FTPSD JOBNAME FTPSD      ; FTPS SERVER
> ENDAUTOLOG
> PORT
>    989 TCP OMVS                ; FTPS SERVER
>    990 TCP FTPSD     NOAUTOLOG ; FTPS SERVER
>
> Here is the output of running the started task - (system specifics 
> changed for security reasons)
>  08:26:31 ---- IAT6853 THE CURRENT DATE IS MONDAY,    27 JUL 2020 ----
>  08:26:31 IAT4401  LOCATE FOR STEP=FTPD     DD=STEPLIB
> DSN=SYSX.TCPIP.SEZATCP
>  08:26:31 IAT4402 UNIT=3390    ,VOL(S)=XYZZY
>  08:26:31 IAT4401  LOCATE FOR STEP=FTPD     DD=STEPLIB
> DSN=SYSX.TCPIP.XXLOAD
>  08:26:31 IAT4402 STORCLAS=XYZZY, MGMTCLAS=XYZZY
>  08:26:31 IAT4401  LOCATE FOR STEP=FTPD     DD=SYSFTPD
> DSN=SYSX.TCPIP.PARMLIB
>  08:26:31 IAT4402 STORCLAS=XYZZY, MGMTCLAS=XYZZY
>  08:26:31 IAT4401  LOCATE FOR STEP=FTPD     DD=SYSTCPD
> DSN=SYSX.TCPIP.PARMLIB
>  08:26:31 IAT4402 STORCLAS=XYZZY, MGMTCLAS=XYZZY
>  08:26:31  IEF695I START FTPSD    WITH JOBNAME FTPSD    IS ASSIGNED TO USER
> FTPSD   , GROUP XXXXXXXX
>  08:26:31  ACF9CCCD USERID FTPSD    IS ASSIGNED TO THIS JOB - FTPSD
>  08:26:31  IEF403I FTPSD - STARTED - TIME=08.26.31
>  08:26:31  IEF404I FTPSD - ENDED - TIME=08.26.31
> //FTPSD    JOB MSGCLASS=T,                                             *
> // MSGLEVEL=1
> //STARTING EXEC FTPSD
>         1 //FTPSD    JOB MSGCLASS=T,
> *
>           // MSGLEVEL=1
>         2 //STARTING EXEC FTPSD
>         3 XXFTPSD  PROC MODULE='FTPD',PARMS='TRACE PORT 990'
>         4 XXFTPD   EXEC PGM=&MODULE,REGION=0M,TIME=NOLIMIT,
>           XX      PARM='POSIX(ON) ALL31(ON)/&PARMS'
>           IEFC653I SUBSTITUTION JCL -
> PGM=FTPD,REGION=0M,TIME=NOLIMIT,PARM='POSIX(ON) ALL31(ON)/TRACE PORT 990'
>         5 XXSTEPLIB  DD DSN=SYSX.TCPIP.SEZATCP,DISP=SHR
>         6 XX         DD DSN=SYSX.TCPIP.XXLOAD,DISP=SHR
>         7 XXCEEDUMP  DD SYSOUT=*
>         8 XXSYSOUT   DD SYSOUT=*
>         9 XXSYSFTPD DD DISP=SHR,DSN=SYSX.TCPIP.PARMLIB(FTPSSL)
>        10 XXSYSTCPD DD DISP=SHR,DSN=SYSX.TCPIP.PARMLIB(TCPDATA)
>  STMT NO. MESSAGE
>         2 IEFC001I PROCEDURE FTPSD WAS EXPANDED USING SYSTEM LIBRARY 
> SYSX.PROCLIB
> IEF695I START FTPSD    WITH JOBNAME FTPSD    IS ASSIGNED TO USER FTPSD   ,
> GROUP USSGRPX
> IEF043I Actions taken by SMFLIMxx parmlib policy for FTPSD    FTPD
>         Step MEMLIMIT set to ONOUDONT by policy - SMFLIM00 0002 
> IEF142I FTPSD FTPSD - STEP WAS EXECUTED - COND CODE 0000
> IEF373I STEP/FTPD    /START 2020209.0826
> IEF032I STEP/FTPD    /STOP  2020209.0826
>         CPU:     0 HR  00 MIN  00.08 SEC    SRB:     0 HR  00 MIN  00.00
> SEC
>         VIRT:    80K  SYS:   216K  EXT:     2220K  SYS:     9108K
>         ATB- REAL:                    12K  SLOTS:                     0K
>              VIRT- ALLOC:       7M SHRD:       0M
> IEF375I  JOB/FTPSD   /START 2020209.0826
> IEF033I  JOB/FTPSD   /STOP  2020209.0826
>         CPU:     0 HR  00 MIN  00.08 SEC    SRB:     0 HR  00 MIN  00.00
> SEC
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to