RE: Problem with SMTP V5R4

["Jack Tucky" <jacktucky@xxxxxxxxx>]

I had tried that.  Turns out it was QTMSCLEAN data area was out there and
causing SMTP to dump.

Thanks

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Monday, August 08, 2011 4:53 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Problem with SMTP V5R4

Jack,

Bring down SMTP and MSF, and then try this command:

CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*NO)

I got this from the folks at HelpSystems during an issue related to
something similar.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Tucky
Sent: Monday, August 08, 2011 3:45 PM
To: 'Midrange Systems Technical Discussion'
Subject: Problem with SMTP V5R4

A system I'm helping out on recently had problems sending email through
SMTP.

 

When trying to start the SMTP Server, we see this message:

 

MCH3601    Escape                  40   08/08/11  13:32:54.459992  QTMSSRCD
QTCP        *STMT    QTMSSRCD    QTCP        *STMT 

                                     From module . . . . . . . . :
QTMSRECO                                                      

                                     From procedure  . . . . . . :
qtmsclup__Fv                                                  

                                     Statement . . . . . . . . . :   28


                                     To module . . . . . . . . . :
QTMSRECO                                                      

                                     To procedure  . . . . . . . :
qtmsclup__Fv                                                  

                                     Statement . . . . . . . . . :   28


                                     Message . . . . :   Pointer not set for
location referenced.                                  

                                     Cause . . . . . :   A pointer was used,
either directly or as a basing                        

                                       pointer, that has not been set to an
address.                                               

 

CPF3353    Escape                  40   08/08/11  13:32:54.793880  QSPCRSPQ
QSYS        081F     QSCAUTOS    QSYS        0171  

                                     Message . . . . :   Output queue
QSCAPAROQ in QSC2034319 already exists.                      

 

I saw a post from Scott Klement about making sure the TMP directory has the
correct permissions.  I tried the recommended solution and that hasn't fixed
the problem.

 

Not sure if this is related, but the system recently reported a problem to
IBM that the Cache battery was dying.  

 

Appreciate any input.

 

Thanks, Art