× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks Chuck - we know we can do that, but it seems weird that the default for one user switched for no reason.

What he has taken to do is to do his FTPing from PROD01 to TEST01 and doing a GET with a (replace rather than a PUT going the other way.

Blair

"CRPence" wrote in message news:mailman.5995.1370277896.7202.midrange-l@xxxxxxxxxxxx...

On 03 Jun 2013 09:25, B Hamren wrote:
<<SNIP>>
I cannot find a way to change it so that he comes up with current
library of QGPL and NAMEFMT of 0 when going from TEST01 to PROD01.

Any suggestions? <<SNIP>>

Ignoring the issue origin and the apparent incorrect output from the
NAMEFMT feedback... Because the naming format is not always guaranteed
to remain the same, IMO the best way to deal with the issue of a naming
format established as other than what is desired, is to learn to deal
with it. Dealing with the variability is an effective requirement for
scripting; i.e. generally necessary to code scripts to be agnostic with
regard to which naming gets established upon a connection, lest they
suddenly start failing when the assumed naming changes.

Given the HOMEDIR is established for the user as described, but the
NAMEFMT 0 is desirable instead, just issue the following to /correct/
the naming [where the 257 "QGPL" is current library. is the desired
effect; i.e. optionally replace the "qgpl" with a different library name]:

cd /qsys.lib/qgpl.lib
namefmt 0


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.