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



I would not go with the distribution list. You will have to maintain it
on all systems. I would create a profile just for this on the target
system. All other systems will only have to have an entry as *all
MT400. The job to receive the file and process it can run under this
profile and have access to only the necessary files/programs needed just
for the application. Just put something in the user profile description
so you know what the profile if for. Also the password can be set at
*NONE with an initial program of *SIGNOFF and permission of *PUBLIC
*EXCLUDE.



Chris Bipes
Director of Information Services
CrossCheck, Inc.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Turnidge
Sent: Thursday, May 29, 2008 7:33 AM
To: Midrange Systems Technical Discussion
Subject: Distribution Lists vs hard coded user profile

I have a backup application that sends a net file (SNDNETF) from all our
remote sites to a central system. This net file contains the
status/results of the backup on that system. The data is combined into a
file from which a report is generated that goes to management to fulfill
SOX requirements.

I am attempting to remove hard coded user profiles from the programming
so that when/if there is turnover, all that needs to be changed is a
DISTRIBUTION LIST, i.e., an object outside of a program.

The SNDNETF command has the parameter TOUSRID which currently contains
my user profile name followed by the central system: TOUSRID((TURNIDGE
MT400)).
I have created a Distribution List in which an entry contains the same
information: TURNIDGE MT400.
The question I have is this: the parameter is referencing the CENTRAL
system (MT400), and the program now works on ALL the systems. Now I am
setting up a Distribution List (DL), and it appears that I have to have
a DL on each system which contains TURNIDGE MT400. Which then requires
that I change the parameter from a hard coded system name (MT400) to a
variable which contains the local system name. So now I will have,
TOUSRID((BKUPNET + &SYSNAME + )).
Is my conclusion correct? Any suggestions?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.