Re: Email relay -- MIDRANGE-L

This is QATMSMTP from my system. Record 3 was altered only on the file
produced by CPYF, to change part of the name. No other changes.

John McKee

5722SS1 V5R4M0 060210 COPY FILE QUSRSYS/QATMSMTP
CONFIG 05/01/15 14:39:47 Page 1

From file . . . . . : QUSRSYS/QATMSMTP Member . . :

CONFIG Record format . . . . . : QTMSMTPR

Record length . . . : 568

To file . . . . . . : *PRINT

RCDNBR *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5
...+... 6 ...+... 7 ...+... 8 ...+... 9 ...+... 0

1 03 030 0 0 N

2 ?

3 relay.XXXXX.net

4 N QSM QSMRMTAD TCPIP 1 00001

5 Y Y

6 *CCSID *CCSID

7 00850

5722SS1 V5R4M0 060210 COPY FILE QUSRSYS/QATMSMTP
CONFIG 05/01/15 14:39:47 Page 2

RCDNBR *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5
...+... 6 ...+... 7 ...+... 8 ...+... 9 ...+... 0

8 N

9 N

10 Y

11 00 000

12 N *NONE 0030

13 N N N N *NONE

14 QSYS/QSYSWRK

15 *NONE

5722SS1 V5R4M0 060210 COPY FILE QUSRSYS/QATMSMTP
CONFIG 05/01/15 14:39:47 Page 3

RCDNBR *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5
...+... 6 ...+... 7 ...+... 8 ...+... 9 ...+... 0

16 N

17 *ALL

18 *LIST

19 *NONE

20 N

21 N

22 Y

23 00 000

5722SS1 V5R4M0 060210 COPY FILE QUSRSYS/QATMSMTP
CONFIG 05/01/15 14:39:47 Page 4

RCDNBR *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5
...+... 6 ...+... 7 ...+... 8 ...+... 9 ...+... 0

24 N 0030

25 N N N N *NONE

26 QSYS/QSYSWRK

27 *NONE

28 N

29 *ALL

30 *NONE

31 *NONE

5722SS1 V5R4M0 060210 COPY FILE QUSRSYS/QATMSMTP
CONFIG 05/01/15 14:39:47 Page 5

RCDNBR *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5
...+... 6 ...+... 7 ...+... 8 ...+... 9 ...+... 0

32 00000

33 V5R3M0

33 records copied to member or label *N in file QSYSPRT in library QSYS. 0
records excluded.
* * * * * E N D O F C O M P U T E R P
R I N T O U T * * * * *

On Sat, May 2, 2015 at 3:25 PM, CRPence <crpbottle@xxxxxxxxx> wrote:

On 01-May-2015 15:45 -0500, Scott Mildenberger wrote:

<<SNIP>> Here is what my file looks like, obviously some of your
values will be different. I would guess the one marked below might
be POPWDW which I have set to *NONE and the message you get indicates
yours is set to 'N' which is not valid. Check that value, if it isn't
the one then one of the other *NONE's that I have you have a 'N'
which you can change and that might fix the issue. I am at 7.1 so
there could be some minor differences in our files due to that.

10 003 0 0 Y
?
GATEWAY
N QSM QSMRMTAD TCPIP 1 00001
Y Y
*CCSID *CCSID
00819
Y
N
Y
02 001
N *NONE 0030
N N N N *NONE
QSYS/QSYSWRK
*NONE
N
*ALL
*NONE <------- Maybe POPWDW
*NONE
00000
N
Y
N
*NONE
N
*ALL
*NONE

V5R5M0

Although the RRN-18 has an expected and apparently appropriate and
supported Special-Value of *NONE, the RRN-18 is unlikely to store the data
for the POP Send Mail Window (POPWDW) parameter; unlikely, only because the
POPWDW parameter data-type is an integer for which the apparent convention
for the other _known stored parameter values_ of a numeric type are
maintained as numeric digits. Thus the more likely value for the POPPWDW,
is the RRN-20 with the value of 00000 [to which the mapping is presumably
to the special value of *NONE; zero is disallowed, only a range 15 to 65535
is allowed]. That the data for that parameter requires mapping from an
internal representation to a special value, however, makes the string being
formed as 'POPWDW(N)' seem all that much more improbable.

BTW, I found a documented /recovery/ [albeit destructive] for the issue
experienced by the OP. I will await the similar presentation of the data
in the member CONFIG of the file QATMSMTP in QUSRSYS expected as part of
the data in a followup reply on Monday; I should be able to offer what
should be a mostly non-destructive recovery, if that might be more
desirable than the effective reset-to-system-defaults path of /recovery/.

--
Regards, Chuck

--
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.