|
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.
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 ...+... 5RTYMIN(10 003) RTYDAY(0 0) RTYRMTSVR(*NO) /* 0 -> *DFT */
1 03 030 0 0 N
2 ?USRIDDELIM('?')
3 relay.XXXXX.netMAILROUTER('relay.XXXXX.net')
4 N QSM QSMRMTAD TCPIP 1 00001AUTOADD(*NO)
5 Y YFIREWALL(*YES) AUTOSTART(*YES)
6 *CCSID *CCSIDTBLSMTPOUT(*CCSID) TBLSMTPIN(*CCSID)
7 00850CCSID(00850)
8 NJOURNAL(*NO)
9 NALLMAILMSF(*NO)
10 YPCTRTGCHR(*YES)
11 00 000RTYHOUR(00 000) /* 0 -> *DFT */
12 N *NONE 0030DIALSCD(*NO *NONE 0030) /* *NO is a single value */
13 N N N N *NONE??? ??? ???
14 QSYS/QSYSWRKSBSD(QSYS/QSYSWRK)
15 *NONERBLSVR(*NONE) /* ¿maybe? */
16 NMIME8BIT(*NO) /* ¿maybe? */
17 *ALLALWRLY(*ALL) /* ¿must be? -- only one left allowing *ALL */
18 *LISTIFCDMN(*LIST) /* ¿maybe IFCDMN? ¡Moot however¡ */
19 *NONEFTRACN(*NONE) /* ¿maybe? */
20 NPOPWDW(N ) /* ¿must be source of msg CPD0076 */
21 NThe prior RRNs 20 and 21 appear to be a[n accidental] repeat of RRN-8 and RRN-9, as the apparent origin for corruption, and the following appear to be what would be expected for RRNs 10 to 21, such that if they were, then the problem should not occur because rrn-32 minus 12 is rrn-20 which suggests POPWDW(00000) for which 00000 translates to *NONE.
22 Y
23 00 000
24 N 0030
25 N N N N *NONE
26 QSYS/QSYSWRK
27 *NONE
28 N
29 *ALL
30 *NONE
31 *NONE
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 * * *
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.