Re: Problem starting DHCP on V4R4M0 -- MIDRANGE-L

Hello Roger,
give QPGMR *RWX authority to that file and then it should work.
(Explanation: QPGMR is the profile for most autostart
and PJ-Jobs to run under).
Famous bug with this ommitance was in V3R7 when
STRCTP and STRHOSTSVR cmds did not have QPGMR
in their list of "allowed" profiles ....
Neil, didn't you remember this one ?  ;-)

HTH, regards from germany, Philipp Rusch

 -----------------------------------------------------------------
| EDV Beratung Rusch          EDP Consulting Rusch                |
| Philipp Rusch               Mailto: Philipp.Rusch@rusch-edv.de  |
| Am Errlich 9                WWW   : http://www.rusch-edv.de/    |
| D-61191 Rosbach,                                                |
| Germany                                                         |
| Phone: (+49) 6003 3972      Mobile : (+49) 172 89 86 230        |
| Fax  : (+49) 6003 3795                                          |
|                                                                 |
 -----------------------------------------------------------------


"Roger Vicker, CCP" schrieb:

> Hello,
>
> Has anyone had a problem (and hopefully a solution) with DHCP not
> starting automatically (CHGDHCPA AUTOSTART(*YES)) and not being able
> to start it manually/explicitly  with adopted authority? I have a
> customer that wants to use DHCP but can only get it to start by being
> a member of QSECOFR. We have tried a program that adopts QSECOFR
> without any success.
>
> The job log shows:
>  From module . . . . . . . . :   QTODDCNV
>  From procedure  . . . . . . :   qtod_IssueMessage__FPcT1ie
>  Statement . . . . . . . . . :   852
>  Message . . . . :   DHCP attributes file missing or not valid.
>  Cause . . . . . :   DHCP requires an attributes file.  The file that
> it tried
>    to open was /QIBM/USERDATA/OS400/DHCP/DHCP.ATTRIB, and it
> encountered an
>    error.  The error code was 3401.  An error code of 0 indicates that
> the DHCP
>    attributes file exists but that the data was not valid. Any other
> error code
>    indicates a file I/O error occurred. Because of this error, an
> attempt was
>    made to restore the attributes file from default values but that
> was
>    unsuccessful also. Without the attribute information, processing
> was unable
>    to continue. Recovery  . . . :   Use the command "WRKLNK
>    '/QIBM/USERDATA/OS400/DHCP/DHCP.ATTRIB'" and if the DHCP attributes
> file
>
> Authority is:
>                    Data
> Opt  User        Authority
>
>      *PUBLIC     *RX
>
> However I did check the full path and found:
>
>                    Data
> Opt  User        Authority
>
>      *PUBLIC     *EXCLUDE
>      QSECOFR     *RWX
>      QTCP        *RX
>
> Thanks,
>
> Roger Vicker, CCP
>
> --
> *** Vicker Programming and Service *** Have bits will byte ***
> www.vicker.com ***
> Where do you find 100 talking invertebrates? The US Senate
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---