|
I have an system running over DDM files. All user profiles that use this
system have a group profile attached to it. When they sign on, there is a
server authorization entry for QDDMSERVER to the group profile. The job log
shows that it connects with the QDDMSERVER authorization entry profile.
EXCEPT with one application, and only one county. It gives me this in the
job log and attempts to make the DDM connection with the profile I signed
on with, not the profile specified in the server authorization entry. It
only does this with the Marriage License program and only in this county.
Database connection started over TCP/IP.
Message . . . . : Database connection started over TCP/IP.
Cause . . . . . : The database server job 296669/QUSER/QRWTSRVR has been
allocated on system S7*226*0 for handling a new TCP/IP using DDM
protocols.
The connection uses IP address **.*.4.18, port 446, and user ID P**6999
at
the server. The connection has a scope of *ACTGRP level in activation
group
*N with an activation group number of 2.
Database connection ended over TCP/IP.
Authorization failure on DRDA/DDM TCP/IP connection attempt.
Operation on DDM data area OR01P in *LIBL failed.
In the same session, I run a different application, Orphans Court, and
the DDM files connect using the authorization entry profile. Now that a
good DDM connection is established. Marriage License now works.
Database connection started over TCP/IP.
Message . . . . : Database connection started over TCP/IP.
Cause . . . . . : The database server job 296669/QUSER/QRWTSRVR has been
allocated on system S7*226*0 for handling a new TCP/IP using DDM
protocols.
The connection uses IP address **.*.4.18, port 446, and user ID
**OCONC*S
at the server. The connection has a scope of *ACTGRP level in
activation
group *N with an activation group number of 2.
DDM object XXXOR60L in SOMORDDM uses remote object <-- prime the pump
DDM object XXXML50P in SOMMLDDM uses remote object <- failed application
now works
Going into other counties accessing the marriage license program first
works fine. So I do not think it is my marriage license RPG program.
I tried to add a server authorization entry for the data base name, but I
do not know the password for the common user specified. I tried a different
profile that exists on both systems and it still failed. It did show the
authorization entry profile in the job log though, (SOMRDB) instead of the
profile I signed on with. When I went into the orphans court application
in the same session, it used the QDDMSERVER entry to authenticate instead
of the entry I created that references the actual server. If I signoff and
go back into orphans, it does not use SOMRDB, but QDDMSERVER. For some
reason, the marriage license application does not pick up the QDDMSERVER
entry on the authorization list.
Server authorization entries for group profile.
Server User Id
Password stored.
QDDMSERVER (common user)
*YES
SOMRDB (different common user)
*YES
I am on 7.3 they are on 7.2.
Sorry for the long email. But want to try to exhaust everything I can
before putting a post out.
Tom Deskevich
Programmer/Analyst
P: 814-472-6066 x201134
F: 814-472-5019
E: TDeskevich@xxxxxxxxxxxxxxxxxx
2017 E. Main Street,
Ebensburg, Pennsylvania
15931
www.harrislocalgov.com
This message has been sent on behalf of a company that is part of the
Harris Operating Group of Constellation Software Inc.
If you prefer not to be contacted by Harris Operating Group please notify
us.
This message is intended exclusively for the individual or entity to
which it is addressed. This communication may contain information that is
proprietary, privileged or confidential or otherwise legally exempt from
disclosure. If you are not the named addressee, you are not authorized to
read, print, retain, copy or disseminate this message or any part of it. If
you have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
