RE: QMSF failing with TCP5101 folliwng IPL with PTF apply -- MIDRANGE-L

Rob,

I also clear /tmp on each LPAR during IPL.
DSPATR OBJ('/tmp') shows Restricted rename and unlink . . . . . : No

The additional change that Brad is recommending:
STRMSF MSGOPT(*CLEAR) as opposed to the default STRMSF MSGOPT(*RESUME)

Should this be made standard on an IPL.

Thanks
Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, April 17, 2017 9:10 AM
To: Midrange Systems Technical Discussion
Subject: Re: QMSF failing with TCP5101 folliwng IPL with PTF apply

Each quarter, while my system is in a restricted state, I clear out the
/tmp folder.
It's very important that
DSPATR OBJ('/tmp')
shows
Restricted rename and unlink . . . . . : No
This was a default IBM changed some releases back to make themselves look
more like Unix. This caused a lot of issues with emailing because SUZYQ
would generate an email and then some system job would try to send the
email and delete the tmp file and couldn't. Even if they had *ALLOBJ
access.
For awhile IBM even changed this upon every IPL. They were beaten into
submission to stop that crap.
See also:
CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*NO)

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
[1]http://www.dekko.com

-----"MIDRANGE-L" <[2]midrange-l-bounces@xxxxxxxxxxxx> wrote: -----
To: "'Midrange Systems Technical Discussion'" <[3]midrange-l@xxxxxxxxxxxx>
From: "Steinmetz, Paul" <psteinmetz@xxxxxxxxxx>
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Date: 04/16/2017 09:56PM
Subject: QMSF failing with TCP5101 folliwng IPL with PTF apply

I IPL'd this weekend for PTF apply.
QMSF is now failing with TCP5101.
All the TCP5101 are always referring to /tmp/mlt63NNN_MIME.mailtooltmp.

TCP5101 Diagnostic 30 04/16/17 16:36:28.160551
QTMMCUTL QTCP *STMT QTMSFWD QTCP *STMT
From module . . . . . . . . :
QTMMUTLM
From procedure . . . . . . :
qtmf_IssueMessage__FPcT1ie
Statement . . . . . . . . . : 170
To module . . . . . . . . . :
QTMSFWD
To procedure . . . . . . . :
Read_Env_Into_Buf__FPc
Statement . . . . . . . . . : 13
Message . . . . : Integrated File
System file open failed on file
/tmp/mlt63554_MIME.mailtooltmp
Cause . . . . . : The RTCP function
requires the use of an Integrated File
System file
/tmp/mlt63554_MIME.mailtooltmp. The errno return from the call
is 3025. Either this file is
missing, locked or damaged on the system and
cannot be used at this time.
Recovery . . . : Stop Mail System Framework
ie. "ENDMSF" and restart "STRMSF".
Check earlier entries in Job Log for
possible reasons for this failure.
If system storage problem: Check Backup
and Recovery - Basic, SC41-3304,
for the appropriate procedures. Likely
errno values: EBADNAME 3014
invalid file name specified ENOENT 3025
No such file or library ENOSPC
3404 No space available EIO
3006 Input/output error EMFILE
3452 Too many open file handles for
process EACCES 3401
Permission denied ENOMEM 3460 Storage
allocation request failed

When I check for the IFS objects, they do not exist.

CHKPRDOPT PRDID(5770TC1)
Product 5770TC1 release V7R1M0 option *BASE load 2924 correctly installed.
Product 5770TC1 release V7R1M0 option *BASE load 5050 correctly installed.
No errors detected by CHKPRDOPT.

I have an open PMR with IBM, nothing yet

Any thoughts from the group.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

[4]psteinmetz@xxxxxxxxxx<[5]mailto:psteinmetz@xxxxxxxxxx>
[6]http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: [7]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [8]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [9]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [10]http://archive.midrange.com/midrange-l.

Please contact [11]support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: [12]http://amzn.to/2dEadiD
</midrange-l-bounces@xxxxxxxxxxxx></psteinmetz@xxxxxxxxxx>

References

Visible links
1. http://www.dekko.com/
2. mailto:midrange-l-bounces@xxxxxxxxxxxx
3. mailto:midrange-l@xxxxxxxxxxxx
4. mailto:psteinmetz@xxxxxxxxxx
5. mailto:psteinmetz@xxxxxxxxxx
6. http://www.pencor.com/
7. mailto:MIDRANGE-L@xxxxxxxxxxxx
8. http://lists.midrange.com/mailman/listinfo/midrange-l
9. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
10. http://archive.midrange.com/midrange-l
11. mailto:support@xxxxxxxxxxxx
12. http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD