Re: qsyseteuid with CPY to QNTC share

Hi

a. You can CPY to a QNTC share by SBMJOB-ing with USER(CPYUSER)
   CPYUSER being the user profile that exists in the i and the Win domains
and having the
   same password on both. (instead of using qsyseteuid)
b. Another way is to create an NFS share on the Win/Unix target machine ,
mounting this
  share over a directory in the IFS and granting Anounimous write/read
access to this dir .
  (then the CPY looks as if your'e CPY-ing to a local IFS  directory but
actually the file is
  copied to the NFS share on the Windows/Unix machine).
  see this link
http://serverfault.com/questions/151740/how-do-i-set-up-a-windows-nfs-share-so-that-i-can-view-its-contents-on-linux

Gad

message: 5
date: Wed, 13 Jul 2011 15:33:20 -0400
from: Michael Ryan <michaelrtr@xxxxxxxxx>
subject: qsyseteuid with QNTC

Hello all...I'm trying to copy files from the IFS to a QNTC share. If
I sign on as a specific user, I have the authority to copy. I'm trying
to use qsyseteuid so I can run the program as any user. I do a WRKJOB
and see this:

Current user profile  . . . . . . . . . . . :   <special user>
Job user identity . . . . . . . . . . . . . :   <special user>
 Set by  . . . . . . . . . . . . . . . . . :     *DEFAULT

So I would think that I have the authority, but I get an 'insufficient
authority' message when attempting the copy. Is qsyseteuid not the
right procedure?

Thanks in advance...


------------------------------

message: 7
date: Wed, 13 Jul 2011 15:25:58 -0600
from: Gary Thompson <GThompson@xxxxxxxxxxx>
subject: Re: qsyseteuid with QNTC

Michael wrote:

 I'm trying to copy files from the IFS to a QNTC share.
So I would think that I have the authority, but I get an 'insufficient
authority' message when attempting the copy. Is qsyseteuid not the
right procedure?

I think QNTC permissions generally depend on the current user profile and
password
       being a match on the target server...

------------------------------

message: 8
date: Wed, 13 Jul 2011 17:52:10 -0400
from: DrFranken <midrange@xxxxxxxxxxxx>
subject: Re: Connecting Liebert AP341 with IBM 8203-E4A Power 6

YES, the cable must be connected when you apply power to the system. The
UPS signals are passed through that cable to the serial port on the
system unit and is recognized by the firmware. The firmware then sends
the 'UPS connected' message to the message queue listed in the QUPSMSGQ
system value.

    - Larry "DrFranken" Bolhuis

On 7/13/2011 11:13 AM, rob@xxxxxxxxx wrote:

*This message was transferred with a trial version of CommuniGate(r) Pro*
According to

https://www-304.ibm.com/support/docview.wss?uid=nas134af6804d80c8a8586256ef1006c9d12

I need to power off the entire system after connecting that 1827 cable in
order for the system to recognize it.  I do not need to have the cable
from the UPS to the 1827 cable connected also do I?  I may be switching
some cables around, etc.


Rob Berendt

------------------------------

message: 9
date: Wed, 13 Jul 2011 23:50:58 +0000 (UTC)
from: Pete Hall <pete@xxxxxxxxxxxxxx>
subject: Re: qsyseteuid with QNTC

On Wed, 13 Jul 2011 15:33:20 -0400, Michael Ryan wrote:

Hello all...I'm trying to copy files from the IFS to a QNTC share. If I
sign on as a specific user, I have the authority to copy. I'm trying to
use qsyseteuid so I can run the program as any user. I do a WRKJOB and
see this:

Current user profile  . . . . . . . . . . . :   <special user> Job user
identity . . . . . . . . . . . . . :   <special user>
  Set by  . . . . . . . . . . . . . . . . . :     *DEFAULT

So I would think that I have the authority, but I get an 'insufficient
authority' message when attempting the copy. Is qsyseteuid not the right
procedure?

Thanks in advance...

We use the profile handle api for this, to adopt a user profile that we
have created specifically for sending and retrieving files from SMB
(windows) shares in network locations. The user has identical credentials
on the i and on the network. It works just fine, as long as we use a real
(or virtual) host name to access the database. We have not gotten it to
work when we attempt to access the NAS device directly, although we
haven't tried that for a number of years.

--
Pete Hall
pete@xxxxxxxxxxxxxx


------------------------------

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



End of MIDRANGE-L Digest, Vol 10, Issue 1010
********************************************

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.