×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Are you trying to do this by hand? In the configuration dialog is an option to use the user name for the session ID. This results in

WorkStationID=+&USERN*=

And this worked.

I also tried the computer name option in the dialog, which put

WorkStationID=+&COMPN*=

into the *.ws - note that this is a little different from Oliver's post. Maybe there's a difference between versions of PCOMM.

The '*' and '=' at the end have to do with avoiding duplicate names on a single computer and between computers. What is interesting is that, when I do not specify a name (which usually results in QPADEV* names) but have these checked, the names come out as A1 or B2, not generic. This is kind of cool.

HTH
Vern

At 09:39 AM 11/10/2003 +0100, you wrote:
Hi !

I have try to add the WorkStationID=&COMPN*= in my *.ws file
But i still get QPADEV00015.

//Jan

oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx
Sänt av: midrange-l-bounces@xxxxxxxxxxxx
2003-11-10 09:14
Sänd svar till Midrange Systems Technical Discussion

        Ärende: Re: CA400 and WorkStationID
Hi,

>I have creat a *.ws file for ca400 "iseries access". V5R2 and V4R5
>In the file i wan't to have the value WorkStationID="username"
>If i remove the WorkStationID from the *.ws file i get the defualt name
>QPADEV00001

>Is there any varible to WorkStationID, i can use for this in a *ws file ?

You want a line with

WorkStationID=&COMPN*=

in your .ws file. Configure a session manually and lookup the correct
syntax in
your .ws file.

Regards,

Oliver




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2026 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.