Thank you both for the detailed help! I will be sure to do the commands right away and get this working properly.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Saturday, October 26, 2013 11:31 AM
Subject: Re: SNDM Command
The /install/ would best IMO, have effected that Product Library
(PRDLIB) specification with the CRTCMD request; i.e. the onus should not be on the user as installer to effect that by CHGCMD. Something to consider as feedback to the provider.? And...
Even better, having made the product library, into which all of the objects of the utility get created, configurable; e.g. as a /parameter/ to the STRREXPRC. There should be *no* reason that, to get the utility to function properly, anyone would have to effect ADDLIBLE [or EDTLIBL; effectively no difference, the latter just provides a /prettier/ UI].
The installation also might best provide as an option, into which library [the original *CMD object or] a Proxy Command is created. The [proxy] command is best created into their QGPL or some other library from which commonly used utilities are accessed; i.e. a library name that is in either QSYSLIBL or QUSRLIBL. And if the command name is one that uses existing or probable future command-mnemonics [and FWiW the single letter M seems unlikely to be used as a noun mnemonic], then the [proxy] command might best be placed in a library that is above QSYS, or not placed in any such library thus requiring explicit library-qualification to invoke. Note: warning of a situation some had noted as having been experienced with the RUNSQL command.
If the SNDM [or its proxy] is not created by the install into a library already in the user's library list, then even if the /install/ had effected the CRTCMD CMD(SMTP/SNDM) PGM(*LIBL/SNDM) PRDLIB(SMTP) as a more appropriate implementation, the user of the command still would either have to library-qualify their invocations [i.e. issue the command as SMTP/SNDM vs just SNDM at the command-line; the latter is implicitly *LIBL/SNDM], or have to add the library name SMTP to the library list.
Having to Add the library to the library list to enable the unqualified command invocation is just as daft as the command searching for the program *LIBL/SNDM without the command object implicitly establishing the known library of the program as the Product Library. Better IMO to create a proxy command (CRTPRXCMD) into a generally available library, after the original command is created into the utility [aka product] library as part of the install; the WRKCMD *ALL/SNDM helps identify the /product/ library and the location of a proxy command with the same name.
So by itself, the CHGCMD invocation below, although desirable, could be incomplete for the most desirable effect.
On 10/26/13 6:02 AM, TheBorg wrote:
CHGCMD CMD(SNDM) PRDLIB(SMTP)
This causes the command processor to automatically put the SMTP
Library at the top of the user portion of the library list when the
command is being executed, and removes it when command processing is
On 10/25/2013 07:33 AM, Kari Zeglin wrote:
I do not have QSECOFR authority, but I was able to install everything
by using his installation guide. I then did a EDTLIBL and added the
SMTP library. I am assuming maybe I should have done ADDLIBLE?
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l