Very Computer

Hello,

I have a problem with users that are always conected to AS/400, because our
ERP software controls concurrent licenses. I'd like doing something to
disconect a user when he has been connected to the AS/400 during 1 hour and
has not worked.

Is this possible?

Thank you in advance.

Jos Vera / Manufactura Moderna de Metales / Barcelona / Spain

You *could* control this with the QINACT* system values, but this effects all
TCP/IP servers.

Hi,

you can desactivate the users via API .

1-List of signon users
2-Determine idle time of user job
3-Disconnect the job.

Greetings,

Quote:> Hello,

> I have a problem with users that are always conected to AS/400, because
our
> ERP software controls concurrent licenses. I'd like doing something to
> disconect a user when he has been connected to the AS/400 during 1 hour
and
> has not worked.

> Is this possible?

> Thank you in advance.

> Jos Vera / Manufactura Moderna de Metales / Barcelona / Spain

WRKSYSVAL QINACTITV

will work

J.W. Kolthof

On Mon, 13 Nov 2000 23:22:15 +0100, "Jos Vera Lpez"

Use the QINACTITV value in conjunction with his brother, the
QINACT(don't' remember what). In the first you set the value of
maximun idle time, in the second wich action to take (wich might be
disconnect the user, or simply send a message that you will monitor to
decide what action take .
Obelix

Hello,

Combine QINACTITV with: QINACTMSGQ *ENDJOB

In combination whith ERP-software this mihgt cause record-locks, so be
carefull.

J.W. Kolthof

Have a look at our 'Remote View' tool which allows you to look at and take
control of users' sessions.  It can be downloaded here www.precosis.com.au .

With this you can see a list of everyone signed on.  Sort all the jobs by
elapsed time. Then  put F3's beside each screen more than an hour old.  It
will back them out gracefully with a normal job end.

Bernard Burchell
Precosis Pty Ltd
http://www.precosis.com.au

No one seems to have mentioned it, but the whole 'disconnect job'
concept doesn't work with Client Access connections.

Peter

=========================================

Sent via Deja.com http://www.deja.com/
Before you buy.

You can use the system-value: QINACTITV, which disconnects a user after a
certain period.
The system-value QINACTMSGQ tells you what the system does with those
disconnected tasks.

Peter Hageman

"Jos Vera Lpez" schreef:

Quote:> Hello,

> I have a problem with users that are always conected to AS/400, because our
> ERP software controls concurrent licenses. I'd like doing something to
> disconect a user when he has been connected to the AS/400 during 1 hour and
> has not worked.

> Is this possible?

> Thank you in advance.

> Jos Vera / Manufactura Moderna de Metales / Barcelona / Spain

it works with newer versions of os/400 and newer versions of client access.

Hmmm, our development machine is at V4R3 and our main production
machine is V4R4. Most users are currently running V3R2 of CA. I thought
they were pretty recent - what CA version is needed?

When I am talking about disconnect, I mean TRUE disconnect and not job
abnends:

DSCJOB:  The Disconnect Job (DSCJOB) command allows the interactive
user to disconnect all interactive jobs at the workstation and return
to the sign-on display.  The job or jobs that are disconnected from a
work station can be reconnected if the same user signs on the same work
station.

ENDJOB: The End Job (ENDJOB) command ends the specified job and any
associated inline data files.  The job can be on a job queue, it can
be active, or it can have already completed running.

In other words, one command kills the interactive job and the other
just disconnects the job from the workstation (but the job remains
active).

There is nothing worse than automatically (and without considered
judgement) killing interactive jobs simply because a user hasn't
touched the keyboard in a specified period of time.

Peter

=======================================

Quote:> it works with newer versions of os/400 and newer versions of client
access.

Sent via Deja.com http://www.deja.com/
Before you buy.

I have os v3r7 and ca v3r1 and it doesn't work.  I think the ca version is
v3r7??  I read this awhile back.  I could be wrong. Let me know.

Hi again!

OK, results of the test this morning. All tests done on the absolute
latest product releases:

Machine is running OS/400 V4R5

PC1 is running CA/400 full version V3R2 SF64050
PC2 is running CA Express V4R5 SF62213

Using PC5250, via TCP/IP, enter command DSCJOB at command line

Both report error CPF1358: DSCJOB not allowed for Server jobs. Job
x/x/x is either a server job, or a client job with a server job active
at the device.

So, quite simply, the Job Disconnect (as opposed to the "Job Trashing")
function doesn't work with Client Access. It never has done and I don't
think IBM ever designed it to.

Peter

=====================================================

Sent via Deja.com http://www.deja.com/
Before you buy.

Quote:> OK, results of the test this morning. All tests done on the absolute
> latest product releases:

> Machine is running OS/400 V4R5

> PC1 is running CA/400 full version V3R2 SF64050
> PC2 is running CA Express V4R5 SF62213

> Using PC5250, via TCP/IP, enter command DSCJOB at command line

> Both report error CPF1358: DSCJOB not allowed for Server jobs. Job
> x/x/x is either a server job, or a client job with a server job active
> at the device.

> So, quite simply, the Job Disconnect (as opposed to the "Job Trashing")
> function doesn't work with Client Access. It never has done and I don't
> think IBM ever designed it to.

 The exception is when using "named device" support; I don't recall the
 RFC.  But anyway, under Client Access 5250, there should be a "Session"
 configuration option where you can name the device.  If the session can
 start with a named device, the CPF1358 seems not to occur; DSCJOB is
 allowed, and CPC1194 upon signon after the disconnect.

Regards, Chuck
All comments provided "as is" with no warranties of any kind whatsoever.