DEC3000->DECServer90TL->CMM comunication problem

[emi...@gmail.com]

Hi All,
I have a problem with communication between the DEC coomputer and our CMM (coordinate measuring machine: B&S PFx MicroXcel, to be specific) and I was hoping that someone could help me a little to test if the problem is in DEC3000 + DECServer90TL or is it inside the CMM control unit. I have to mention that I do not know much about the VMS, just very basic stuff.

The machine is operated by the software called Quindos. The CMM is connected to port 1 of the DECServer90TL and DECServer connects to the DEC3000 through CentreCOM MR122T Micro repeater.

When starting Quindos we get an error message that it can not connect to the CMM just like the CMM was not powered on - but it is.

I need to know if the DEC3000+DECServer configuration etc. is ok before we call for the CMM service because they are able to check only if the CMM comuter is ok, they do not know anything about DEC and OpenVMS 6. So if it's in DEC it will be money waste, and they are expensive.

Here is what I already was able to check:
- I do not see any error messages during DEC start up on the screen,
- the DECServer90TL device seems to download the necessary software from the DEC3000 correctly because the 3 diodes (on the left side) are lit as written in the manual which means that it communicates with the computer correctly, downloaded a software from DEC and is ready for operation (but none of the 8 port diodes is lit),
- in VMS I was able to connect to the DecServer device (through the commands: mcr ncp) and check the parameters of the ports (I used the info given on this site: http://www3.sympatico.ca/n.rieck/docs/openvms_notes_decserver_lat.html)
to which the CMM and the printer (LA75, port 5) is connected; and it seems that the parameters are set correctly as specified in the QDS_TERMSET.COM file, i.e. for the CMM port: 7bits, parity=even, speed = 4800 (in both directions) and for the printer port: 8bits, parity =none, speed = 9600 (both directions).
- I tried to print something but without success. No mater from where I try to print (i.e. NCP - "test port 5" command, VMS - "print" command, QUINDOS) the printer (LA75) does not respond and the "DEC" diode blinks all the time on the printer (in Quindos: command "Connect printer" lits the port 5 diode on the DecServer device but nothing happens after calling print command).
- I checked for the QUEUEs and there is one set: BATCH$LEITZ but it says it's "autostared but stoped" - I do not know about "queues" so do not know what that means, and I have no idea what could be wrong.
- we tried to connect a PC with WinXP to the DECServer ports through RS232 and "listen" on the Hyperterminal software to the ports (setting appropriate transmission parameters) but without any success. On the other hand, we are not sure about the wiring between the RJ45 -> RS323 (9 pins).

I'm hoping that there is some setting in the VMS lost for "lighting up" the ports.

Does anyone have any ideas what can I check/test?

I'd be grateful for any help
regards

Wojtek

ps.
I do not know if following could be connected with it but the problems
occurred after a day when we received message "not enough free blocks on disk"
during saving a programme in Quindos. what I did at that time was
"purge" whole disk I think, could I delete some system files with that?
And I could not print at that day also but again: I haven't try to print
before that day neither.

[abrsvc]

There are a number of potential problems that can exist here.

1) The serial connection between the DECserver and the target machine is not working
2) The software that should be communicating with the target machine is not working
3) The DECserver itself has a problem
etc...

Without additional information and some poking around with various hardware and software, it is unlikely that much assistance will be forthcoming here.

If there is a way to connect to the system remotely (and securely) there are many of us here that can take a look and hopefully provide some guidance.

I can say that I have setups similar to what you describe that are working without fail as we speak. The methodology works, what remains is to determine why your configuration failed and continues to fail.

RE: purging the disk.

As long as teh command used was PURGE, you are not likely to have created a problem with the cleaning of the disk. If you used DELETE, then yes, you could have removed vital software.

Can you provide more details or direct contact info?

Thanks,
Dan

[Bob Gezelter]

Wojtek,

The description is consistent with any number of problems, both in hardware and software. The PURGE command would be unlikely to damage system files, but it could cause a problem for the application (depending upon precisely what was purged).

The "Disk full" and the network issue could also be completely unrelated. The problem could be in the printer. Another possibility is that the application that is connected to the printer went into a strange state when the disk filled unexpectedly.

It is hard to assist without in-depth details. If we can be of assistance, please let me know, assisting clients with technical problems is what we do.

- Bob Gezelter, http://www.rlgsc.com

[Stephen Hoffman]

On 2013-04-18 14:38:19 +0000, emi...@gmail.com said:

> I do not know if following could be connected with it but the problems
> occurred after a day when we received message "not enough free blocks
> on disk" during saving a programme in Quindos.

Free up some (more) space and/or migrate to larger disks (or both), and
try an OpenVMS system reboot, as some application software can get
tangled on disk-full errors, and a reboot (now with free space) can
sometimes clear up the resulting tangled process state.

Otherwise, somebody is probably going to need to rummage around within
this configuration.

About the only thing I can state for certain from what was posted is
that you're either paying your CMM vendor far too little (to allow them
to get the help that you need) or you're paying too much (for the help
that you've gotten).....


--
Pure Personal Opinion | HoffmanLabs LLC

[Christoph Gartmann]

In article <a3e52044-60ae-4ca9...@googlegroups.com>, emi...@gmail.com writes:

>The machine is operated by the software called Quindos.

Where does this Quindos run on? On the DEC computer under VMS?

>The CMM is connected to port 1 of the DECServer90TL and DECServer connects
>to the DEC3000 through CentreCOM MR122T Micro repeater.

Ok.

>When starting Quindos we get an error message that it can not connect to the
>CMM just like the CMM was not powered on - but it is.

[..]

>Here is what I already was able to check:
>- I do not see any error messages during DEC start up on the screen,

This is good.

>- in VMS I was able to connect to the DecServer device (through the
> commands: mcr ncp) and check the parameters of the ports

So the network connection between your VMS system and the DECserver is all
right.

>- I tried to print something but without success.

Here is the important part. How do the VMS system and the DECserver
communicate? I assume this is via LAT. Could you post your
sys$manager:lat$systartup.com
?

>- I checked for the QUEUEs and there is one set: BATCH$LEITZ but it says
> it's "autostared but stoped" - I do not know about "queues" so do not
> know what that means, and I have no idea what could be wrong.

I assume the queu should be "idle". But I don't think it is relevant for the
connection problem. Please post the output of
SHOW QUEUE/FULL/ALL

>Does anyone have any ideas what can I check/test?

Quite a few of them. But I need more information ;-)

>I do not know if following could be connected with it but the problems
>occurred after a day when we received message "not enough free blocks on
>disk" during saving a programme in Quindos.

This might be the cause for your trouble.

>what I did at that time was "purge" whole disk I think, could I delete some
>system files with that?

No, but this is not the approach I would choose. Something is filling up your
disk. The question is what? And how?

Regards,
Christoph Gartmann

--
Max-Planck-Institut fuer Phone : +49-761-5108-464 Fax: -80464
Immunbiologie und Epigenetik
Postfach 1169 Internet: gartmann@immunbio dot mpg dot de
D-79011 Freiburg, Germany
http://www.immunbio.mpg.de/home/menue.html

[Jan-Erik Soderholm]

Just a point noone has commented yet...

emi...@gmail.com wrote 2013-04-18 16:38:

> No mater from where I try to print (i.e. NCP - "test port 5" command...

This is a command local to the DECserver. It has
nothing to do with the VMS system at all.

If the printer can accept plain text it should write
lines with "ABCDEF........"

Has this worked before?
If so, you have some problem with the wiring, baudrate or similar.

> VMS - "print" command, QUINDOS) the printer (LA75) does not respond.

> and the "DEC" diode blinks all the time on the printer

So the printer *does* react on the print at all !?
Not by printing, but by blinking some LED (?).

This also points to some setup error. Baudrate or similar.


Regards,
Jan-Erik.

[VAXman-]

In article <kkp2eo$nsc$1...@speranza.aioe.org>, gart...@nonsense.immunbio.mpg.de (Christoph Gartmann) writes:
>In article <a3e52044-60ae-4ca9...@googlegroups.com>, emi...@gmail.com writes:
>
>>The machine is operated by the software called Quindos.
>
>Where does this Quindos run on? On the DEC computer under VMS?

I thought Quindos was a sandwich shop. :P

--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.

[abrsvc]

Quindos software drives a measurement device(CMM) connected through the DECserver. There is no printer involved as others have posted. I would suspect that the batch queu being stopped may have something to do with this malfunction as well.

Try START/QUEUE BATCH$LEITZ from the $ prompt. If you are lucky, that may free up the background interface code that interacts with the machine.

Let us know,

Dan

[Bob Koehler]

In article <00AD1FB2...@SendSpamHere.ORG>, VAXman- @SendSpamHere.ORG writes:
>
> I thought Quindos was a sandwich shop. :P
>

There's the problem. Somebody ran the system through a toaster.

(TOA0: anyone?)

[David Froble]

Any environment can develop problems. When such occur, it's usually
necessary to be able to understand any diagnostics the system is issuing.

I'm guessing that at one time you had personnel that set up the system,
or that your third party vendor had such personnel. If such personnel
are no longer available, then at some time you're going to end up
without the system performing.

I'm guessing that you've been able to exist for some time without the
availability of knowledgeable people being available. If anything, this
is a testament to the robustness of your system. Perhaps it's not cost
effective to have full time support personnel.

You didn't specify your location. One possible solution to your long
term requirements would be to find several consultants who know VMS and
serial communications using terminal servers. Pay some small amount to
have these people / organizations to learn your environment, to perhaps
do some tune-up on your VMS system, and therefore be available should
you have need of them. Such services are available, and local usually
is better than remote. Might someday have a need to get hands on the
hardware.

[Steven Schweda]

> - we tried to connect a PC with WinXP to the DECServer ports
> through RS232 and "listen" on the Hyperterminal software to
> the ports (setting appropriate transmission parameters) but
> without any success. On the other hand, we are not sure about
> the wiring between the RJ45 -> RS323 (9 pins).

Sounds reasonable, if you could trust your cable.

I normally use null-modem cables with 25-pin connectors,
and then 25-pin-to-9-pin adapters when I want to connect to a
9-pin serial port on a computer. The result seems to be as
follows (which will look better with a fixed-width font):

DS90TL port (F)

i i o - o o o i in/out
1 2 3 4 5 6 7 8
Rgnd RXD Tgnd CTS RTS TXD DTR DSR
Gnd (nc) +-----------+

---------------------____--------------------


D-9 (F)
5 4 3 2 1
9 8 7 6


DCE DS90
D9F RJ
+-- DCD 1 - 8 DSR
| TXD 2 - 6 TXD
| RXD 3 - 2 RXD
| DSR 4 - 7 DTR ----+
| GND 5 - 1 Rgnd |
| 3 Tgnd |
+-- DTR 6 - 8 DSR |
CTS 7 - 5 RTS ----+
RTS 8 - 4 CTS
RI 9 - nc

Pins 1 and 6 of the D-9 connector are joined in my
(null-modem) cable. Pins 5 and 7 of the DS90 are joined by
the DS90. I don't claim that it's all correct, but it seems
to work here, so it should be adequate for your testing.

[David Froble]

The major problem with this description is, from what direction is the
plug (DB9) (RJ45) being observed ....

:-)

Ask me how I know this ....

[Steven Schweda]

> The major problem with this description is, from what direction is the
> plug (DB9) (RJ45) being observed ....

Ignoring the lack of ambiguity in the D-9 diagram, the
view is looking at the holes in the female "(F)" connectors.
If they has been viewed from behind (that is, from the wire
side), then I'd've needed to use dotted lines.

[Bill Gunshannon]

In article <kkpqqu$etb$1...@dont-email.me>,

What difference wold that make? Every DB9 I have ever seen had the
numbers embossed on the connector.

bill

--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
bill...@cs.scranton.edu | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>

[emi...@gmail.com]

Hi All,
thank you very much for all you comments. Sorry for answering so late but I had to work over the weekend (evening students) - I really do appreciate your help.

my direct contact info:
emilwp at gmail.com, or wplowucha at ath.eu
Laboratory of Metrology, University of Bielsko-Biala

About the blinking on the printer: it's bliking all the time the same - no reaction on the issued commands. And as far as I remember to be able to print the diode was to be lit.

The answers to Christof comments follow below:

> In article <a3e52044-60ae-4ca9...@googlegroups.com>, emi...@gmail.com writes:
>
>
>
> >The machine is operated by the software called Quindos.
>
>
>
> Where does this Quindos run on? On the DEC computer under VMS?
>

yes, it runs on the DEC3000 under VMS

>
>
[...]

>
> >- I tried to print something but without success.
>
> Here is the important part. How do the VMS system and the DECserver
>
> communicate? I assume this is via LAT. Could you post your
>
> sys$manager:lat$systartup.com
>
> ?

Yes it's LAT - at least the ports' configuration says that it's default protocol.


Here is the lat&systartup.com (I was thinking about removing commented lines but was not sure if it's site-specific or VMS-standard - sorry for long post):


$! Copyright (c) 1990 Digital Equipment Corporation. All rights reserved.
$!
$! LAT$SYSTARTUP.COM -- LAT Startup Commands Specific to Site
$!
$! Use this command procedure to customize the LAT characteristics for
$! the local node. These commands, which should serve as examples,
$! will set up a LAT service name SYS$NODE and default identification
$! SYS$ANNOUNCE. The LAT service name and identification will default
$! to SYS$NODE and SYS$ANNOUNCE unless you specify a service name and
$! identification as arguments to the command line that invokes
$! LAT$STARTUP.COM:
$! $ @SYS$STARTUP:LAT$STARTUP
$!
$! You can specify other node and service characteristics (such as group
$! codes) as arguments to this command line, as shown below.
$!
$! Argument Function
$! --------- --------
$!
$! P1 Name of the service to be created. If not supplied, a
$! service will be created with the same name as the node.
$!
$! P2,P3,P4 Parameters and qualifiers to the SET NODE command.
$!
$! P5 Parameters and qualifiers to the SET SERVICE command.
$! P5 is only used if P1 is specified. More than one
$! argument may be supplied by enclosing the string in
$! quotes.
$!
$! Example: $ @SYS$STARTUP:LAT$STARTUP HAWK "/IDENTIFICATION=" -
$! """""Development node"""""
$!
$! Please review and edit this file for possible additions and deletions
$! that you wish to make. Future software updates will not overwrite the
$! changes made to this file.
$!
$ required_privileges = "OPER"
$ prev_privs = f$setprv(required_privileges)
$ if .not. f$privilege(required_privileges) then goto no_privileges
$ lcp := $latcp
$!
$! --------------------- Modify Node Characteristics ------------------------
$!
$ lcp set node 'p2' 'p3' 'p4'
$!
$! Some examples:
$!
$! ** Allow incoming connections only
$!
$! lcp set node /connections=incoming /groups=(enable=(12,40,43,73),disable=0)
$! lcp set node /connections=incoming /groups=enable=(0-255)
$!
$! ** Allow outgoing connections only
$!
$! lcp set node /connections=outgoing /user_groups=enable=(24,121-127)
$! lcp set node /connections=outgoing /user_groups=(enable=0-255) /node_limit=50
$!
$! ** Enable incoming and outgoing connections
$!
$! lcp set node /connections=both /group=enable=(43,73) /user=enable=(44,56)
$! lcp set node /connections=both /group=enable=(0-255) /user=enable=(0-255)
$!
$!
$! -------------------- Modify Service Characteristics ----------------------
$!
$ if p1 .eqs. ""
$ then
$ lcp create service
$ else
$ lcp create service 'p1' 'p5'
$ endif
$! ------------------------- Start LAT Protocol -----------------------------
$!
$ lcp set node /state=on
$!
$!
$! ------------------------- Create and Map Ports ---------------------------
$!
$! Some examples:
$!
$! lcp create port lta101: /dedicated
$! lcp create port lta102: /application
$! lcp create port lta103: /application
$! lcp create port /nolog/logical=(name=ln03$mgmt, table=system, mode=executive)
$!
$! lcp set port lta101: /dedicated /service=graphics
$! lcp set port lta102: /node=server_1 /port=port_1
$! lcp set port lta103: /node=server_2 /service=laser
$! lcp set port ln03$mgmt: /node=server_3 /service=ln03_printers
$!
$exit:
$ prev_privs = f$setprv(prev_privs)
$ exit
$!
$no_privileges:
$ write sys$output "Insufficient privileges to execute LATCP commands."
$ write sys$output "Requires ",required_privileges," privileges."
$ goto exit

-----end of file

>
>
>
> >- I checked for the QUEUEs and there is one set: BATCH$LEITZ but it says
>
> > it's "autostared but stoped" - I do not know about "queues" so do not
>
> > know what that means, and I have no idea what could be wrong.
>
>
>
> I assume the queu should be "idle". But I don't think it is relevant for the
>
> connection problem. Please post the output of
>
> SHOW QUEUE/FULL/ALL
>
>

the answer is:

Batch queue BATCH$LEITZ, stoped, autostart inactive, on LEITZ::
/AUTOSTART_ON=(LEITZ::) /BASE_PRIORITY=4 /JOB_LIMIT=8 /OWNER=[SYSTEM]
/PROTECTION=(S:M,O:D,G:R,W:S)

and below are 2 entries with stopped print jobs (my trials from a few days back), both having STATUS: "Pending (queue stoped)"

I found file SYS$MANAGER:SYSTARTUP_VMS.COM in which there is something about the queues. The line "start/queue/manager" was added a few year back when we also had some problems - unfortunatelly the guy who did it is retired.



$!
$! SYS$MANAGER:SYSTARTUP_VMS.COM
$!
$! This is the template for the site-specific startup command procedure.
$!
$ WRITE SYS$OUTPUT ""
$ WRITE SYS$OUTPUT "The OpenVMS system is now executing the site-specific startup commands."
$ WRITE SYS$OUTPUT ""
$!
$! You may add commands to this procedure or change the commands within this
$! procedure as needed for your system. This command procedure is saved when
$! you upgrade or update to a new version of VMS. Other startup command
$! procedures are replaced with each release of VMS. Place symbol definitions
$! from startup procedures that will be replaced when you upgrade to a new
$! release of VMS in this command procedure. In this way, you can save symbol
$! definitions from one VMS release to the next.
$!
$! NOTE: Many command line are commented out. This allows you to to decide
$! what and how some commands are to be executed. Also note that these lines
$! begin with the "$!$" character sequence. Remove the first two characters "$!"
$! if you wish to have one of these commands executed. Pay close attention to
$! whether any of these commands are continuation type lines (hyphen at end of
$! line). If so you will be required to remove the "$!" characters from the
$! start of additional lines. Continuation lines do not start with a "$".
$!
$! OPCOM is started by default on all VMS systems. However, by default, operators
$! will not be able to satisfy user mount requests. To allow operators to
$! satisfy user mount requests, edit the SYS$MANAGER:SYLOGIN command procedure
$! by removing the command line that equates MOUNT to MOUNT/NOASSIST.
$!
$! The following commands install the secondary page file, if it exists.
$! (Note that the secondary swap file is installed by the command procedure
$! SYS$SYSTEM:STARTUP.COM if it exists.)
$!
$ IF F$SEARCH("SYS$SYSROOT:<SYSEXE>PAGEFILE1.SYS") .NES. ""
$ THEN SYSGEN = "$SYSGEN"
$ SYSGEN INSTALL SYS$SYSROOT:<SYSEXE>PAGEFILE1.SYS /PAGEFILE /NOCHECK
$ ENDIF
$!
$! Set up virtual terminals
$!
$ SYSMANIO = "$SYSMAN IO"
$!$ SYSMANIO CONNECT VTA0/NOADAPTER/DRIVER=SYS$LOADABLE_IMAGES:SYS$TTDRIVER.EXE
$!
$! This command defines a system-wide login command procedure for all users.
$!
$ DEFINE /SYSTEM /EXEC SYS$SYLOGIN SYS$MANAGER:SYLOGIN
$!
$! This command defines a message to be displayed before each user logs in.
$!
$ DEFINE /SYSTEM SYS$ANNOUNCE "@SYS$MANAGER:ANNOUNCE.TXT"
$!
$! This command defines a message or file to be displayed after each user logs in.
$!
$!$ DEFINE /SYSTEM SYS$WELCOME "@SYS$MANAGER:WELCOME.TXT"
$!
$!
$! Set up a print queue.
$!
$! Choose the device you will use for printing. Define the logical name
$! $PRINTER to name the device you will use for printing; either remove the
$! comment delimiter ($!) from one of the following commands or add a command
$! in the following format.
$!
$!$ DEFINE /SYSTEM $PRINTER $TERMINAL0 ! if a hard copy terminal is the printer
$!$ DEFINE /SYSTEM $PRINTER _LPA0: ! if using a line printer
$
$!
$! If you will use a line printer, set the printer characteristics.
$! Delete the comment characters from the following line.
$!
$!$ SET PRINTER /NOWRAP /NOTRUNCATE /CR $PRINTER
$
$!
$! If you will use a hard copy terminal as the print device, set the terminal
$! characteristics. The following terminal characteristics vary from one
$! hard copy terminal to another: speed, width, length, and device type.
$! If your terminal is an LA100, remove the comment characters from the
$! following command lines. If your terminal is not an LA100, add a command in
$! the following format.
$!
$!$ SET TERMINAL $PRINTER /PERMANENT /NOBROADCAST /NOTYPEAHEAD /NOWRAP -
$! /SPEED=(1200) /WIDTH=(132) /PAGE=(66) /DEVICE_TYPE=(LA100)
$
$!
$! To set your printing device as spooled to the queue SYS$PRINT,
$! remove the comment characters in the following command line.
$!
$!$ SET DEVICE /SPOOLED=(SYS$PRINT, SYS$SYSDEVICE:) $PRINTER
$!
$! The following command will enable autostart queues to start on this
$! node. To enable autostart during startup, remove the comment
$! delimiter (!) from the following command line.
$!
$! Make sure resources required by all autostart queues are available,
$! such as disks and printing devices.
$!
$! *****************************************************************
$! ************************ wstawiono linie ponizej - 22.01.2007
$!
$ start/queue/manager
$!
$!
$ ENABLE AUTOSTART /QUEUES
$!
$! If your SYS$PRINT queue is not an autostart queue, then remove the comment
$! character from the following command to start the queue.
$!
$!$ START /QUEUE SYS$PRINT
$
$!
$! To start a batch queue, remove the comment character from the
$! following command line.
$!
$! START /QUEUE SYS$BATCH
$
$!
$! To use asynchronous DECnet, set the terminal line characteristics.
$! Change the following SET TERMINAL command to specify the terminal line
$! you will use. Remove the comment delimiter ($!) from the SET TERMINAL
$! command line. (Reminder: To set the terminal line characteristics for the
$! other side of the asynchronous connection, enter a SET TERMINAL command
$! on the routing node to which you are connecting.)
$!
$!$ SET TERMINAL $TERMINAL1 /PERMANENT /NOAUTOBAUD /SPEED=9600 /PROTOCOL=DDCMP
$!
$! Following are the commands that start up the DECnet network, if you
$! installed the DECnet software. Note that only one of these commands is
$! needed to start the network, the other should be commented out. Configure
$! the network and define the other node names before starting up DECnet;
$! otherwise you will get error messages stating that the database is not
$! initialized.
$!
$! If you have batch queues set up on your system, insert a comment delimiter
$! ($!) before the dollar sign in the first command line below. Remove the
$! comment delimiter from the second and third command lines below. This
$! allows the system to startup more quickly, and decreases the amount of
$! time you must wait to log in.
$!
$!
$ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET
$!$ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" - !This is faster, if you
$! THEN SUBMIT SYS$MANAGER:STARTNET.COM !have batch queues set up.
$!
$! Once you have removed the comment delimiter from one of the above commands,
$! insert a comment delimiter ($!) before the dollar sign in the command line
$! below. The logical is only required if the DECnet network has not been started.
$!
$ DEFINE DECW$IGNORE_DECNET TRUE
$!
$! The following command should be used only if you do not wish the DECwindows
$! startup file to be run. The DECwindows startup file should be run on all
$! types of machines, even if they are not using a DECwindows display. If
$! you wish to run the DECwindows startup file at a later time during system
$! startup remove the comment from the line below.
$!
$!$ DEFINE DECW$IGNORE_DECWINDOWS TRUE
$!
$!
$ DEFINE/SYSTEM/EXEC DECW$LOGINLOGO SYS$MANAGER:LEITZ_QUINDOS_LOGO.COM
$!
$!This definition is necessary for DECserver software
$ DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG -
MOM$LOAD MOM$SYSTEM, SYS$SYSROOT:[DECSERVER], -
SYS$SYSDEVICE:[VXT$LIBRARY]
$!
$! mount disk dka200: and dka500: if found
$ IF (F$GETDVI("DKA200:", "EXISTS")) THEN MOUNT/SYS/NOASSI DKA200: USERDISK
$
$ IF (F$GETDVI("DKA500:", "EXISTS"))
$ THEN DEFINE/SYS/EXE QDS_BDISK DKA500:
$ SET SECURITY/CLASS=DEVICE/PROT=W:RWLP QDS_BDISK
$ ENDIF
$
$! start LAT
$ @SYS$STARTUP:LAT$STARTUP.COM
$
$! start VXT support
$ @SYS$STARTUP:VXT$STARTUP.COM
$ @SYS$MANAGER:QDS_DEFINE_FONTS.COM
$!
$! analyze and repair system disk
$ ANALYZE/DISK/REPA SYS$SYSDEVICE:
$
$ EXIT

-----end of file


I tried before:

START/QUEUE BATCH$LEITZ
but there was an error message - do not remember now exactely what it said, I'll check tommorow.


regards

Wojtek

[emi...@gmail.com]

[...]

>
>
> Try START/QUEUE BATCH$LEITZ from the $ prompt. If you are lucky, that may free up the background interface code that interacts with the machine.
>

the answer is:
%JBC-I-AUTONOTSTART, queue is autostart active, but not started


Wojtek

[Jan-Erik Soderholm]

First, always (if possible, as in this case) supply both the
message *and* the command producing it as-is. Cut-n-pased.

Second, didn't "$ help /message AUTONOTSTART" tell you anything?


Jan-Erik.

[Christoph Gartmann]

In article <c470f552-78a4-4ae2...@googlegroups.com>, emi...@gmail.com writes:
>> In article <a3e52044-60ae-4ca9...@googlegroups.com>, emi...@gmail.com writes:
>> Where does this Quindos run on? On the DEC computer under VMS?
>>
>yes, it runs on the DEC3000 under VMS

Ok.

>> >- I tried to print something but without success.
>>
>> Here is the important part. How do the VMS system and the DECserver
>>
>> communicate? I assume this is via LAT. Could you post your
>>
>> sys$manager:lat$systartup.com
>>

>Yes it's LAT - at least the ports' configuration says that it's default
>protocol.
>
>
>Here is the lat&systartup.com (I was thinking about removing commented lines
>but was not sure if it's site-specific or VMS-standard - sorry for long post):

The startup procedure is in DCL, the script language of OpenVMS. You are
right, the "!" indicates a comment.

>
>$ lcp set node /state=on

That's all I can find here. So your system is running LAT but I don't know
what is started. Have a look at SYS$MANAGER:SYSTARTUP_VMS.COM and post the
line that calls the LAT startup procedure.

>> connection problem. Please post the output of
>>
>> SHOW QUEUE/FULL/ALL
>>
>>
>
>the answer is:
>
>Batch queue BATCH$LEITZ, stoped, autostart inactive, on LEITZ::
> /AUTOSTART_ON=(LEITZ::) /BASE_PRIORITY=4 /JOB_LIMIT=8 /OWNER=[SYSTEM]
> /PROTECTION=(S:M,O:D,G:R,W:S)
>
>and below are 2 entries with stopped print jobs (my trials from a few days
>back), both having STATUS: "Pending (queue stoped)"

Then the queue handles the printing. But you missed to post the output of the
two jobs...

>I found file SYS$MANAGER:SYSTARTUP_VMS.COM in which there is something about
>the queues. The line "start/queue/manager" was added a few year back when
>we also had some problems - unfortunatelly the guy who did it is retired.

The command above starts the so called "queue manager". It is pretty common
on OpenVMS systems.

>$ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET

So you have DECNET running.

>$ DEFINE/SYSTEM/EXEC DECW$LOGINLOGO SYS$MANAGER:LEITZ_QUINDOS_LOGO.COM
>$!
>$!This definition is necessary for DECserver software
>$ DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG -
> MOM$LOAD MOM$SYSTEM, SYS$SYSROOT:[DECSERVER], -
> SYS$SYSDEVICE:[VXT$LIBRARY]
>$!
>$! mount disk dka200: and dka500: if found
>$ IF (F$GETDVI("DKA200:", "EXISTS")) THEN MOUNT/SYS/NOASSI DKA200: USERDISK
>$
>$ IF (F$GETDVI("DKA500:", "EXISTS"))
>$ THEN DEFINE/SYS/EXE QDS_BDISK DKA500:
>$ SET SECURITY/CLASS=DEVICE/PROT=W:RWLP QDS_BDISK
>$ ENDIF
>$
>$! start LAT
>$ @SYS$STARTUP:LAT$STARTUP.COM

Strange. There is nothing configured. What do you see when you enter:
SHO DEV LTA

[emi...@gmail.com]

>
>
> First, always (if possible, as in this case) supply both the
>
> message *and* the command producing it as-is. Cut-n-pased.
>
>
>

Sorry, but I cann't copy paste because I'm not posting from the problematic computer - I'm re-typing :(

> Second, didn't "$ help /message AUTONOTSTART" tell you anything?
>
>

As said, I'm newbe with the VMS - my knowledge does not go too far from: dir, type, set def , show.

Anyway the help says:

"An attempt was made to start an autostart queue when none of its available nodes has autostart enabled"

and

"Enter an ENABLE AUTOSTART /QUEUES command on th enodes in the queue's autostart node list"

this command (ENABLE AUTOSTART /QUEUES ) is in one of the file processed during system startup (at least I hope so) namely SYS$MANAGER:SYSTARTUP_VMS.COM which I posted previously. does it mean that the file is NOT processed?

after entering:

SYS>ENABLE AUTOSTART /QUEUES
SYS>start /queue batch$leitz
%JBC-E-STARTED, queue already stared

but:
SYS>print /queue=batch$leitz welcome.txt
Job WELCOME (queue BATCH$LEITZ, entry 3) strated on BATCH$LEITZ

does not move the printer

Wojtek

[emi...@gmail.com]

>
>
> Strange. There is nothing configured. What do you see when you enter:
>
> SHO DEV LTA
>

SYS>SHO DEV LTA


Device Device Error
Name Status Count
LTA0: Offline mounted 0
LTA101: Online 0
LTA102: Online 0
[...]
LTA108: Online 0
LTA5003: Online 0


I did a few minutes before:
ENABLE AUTOSTART /QUEUES

[Jan-Erik Soderholm]

emi...@gmail.com wrote 2013-04-23 13:13:
>
>>
>>
>> First, always (if possible, as in this case) supply both the
>>
>> message *and* the command producing it as-is. Cut-n-pased.
>>
>>
>>
>
> Sorry, but I cann't copy paste because I'm not posting from the
> problematic computer - I'm re-typing :(
>

OK. :-)
But then, at least try to re-type your commands used also.

>> Second, didn't "$ help /message AUTONOTSTART" tell you anything?
>>
>>
>
> As said, I'm newbe with the VMS - my knowledge does not go too far from:
> dir, type, set def , show.
>
> Anyway the help says:
>
> "An attempt was made to start an autostart queue when none of its
> available nodes has autostart enabled"
>
> and
>
> "Enter an ENABLE AUTOSTART /QUEUES command on th enodes in the queue's
> autostart node list"
>

Exactly! Very clear on what was missing, not ? :-)

> this command (ENABLE AUTOSTART /QUEUES ) is in one of the file processed
> during system startup (at least I hope so)

Verify!

> namely
> SYS$MANAGER:SYSTARTUP_VMS.COM which I posted previously. does it mean
> that the file is NOT processed?

Systartup_vms.com is most certenly processed. But the enable autostart
command might not be. There might some logic in the startup that
prevents it from been executed, or something else is not in the
correct state when it is executed. One need the output from
a clean boot to tell wht is happening.

>
> after entering:
>
> SYS>ENABLE AUTOSTART /QUEUES
> SYS >start /queue batch$leitz
> %JBC-E-STARTED, queue already stared
>

So ENABLE AUTOSTART /QUEUES seems to have fixed the problem
with the queue as such. You have to look over your startup
routines/scripts why this was not run at startup.

> but: SYS>print /queue=batch$leitz welcome.txt Job WELCOME (queue
> BATCH$LEITZ, entry 3) strated on BATCH$LEITZ
>

Now, as you have seen, batch$leitz is a *BATCH* queue !
Not only from it's name (BATCH$LEITZ), but also from
the output of SHOW QUEUE :

> the answer is:
>
> Batch queue BATCH$LEITZ,...............

Note "Batch queue..." in the output above!

Batch queues are for running batch jobs, *not* for printing!

A batch job (running on BATCH$LEITZ) can of course print things,
but using another queue, a "Printer queue", "Server queue" or such,
it depends on what method/protocol is used for the printer.


Jan-Erik.

> does not move the printer
>
> Wojtek
>

So ENABLE AUTOSTART /QUEUES seems to have fixed the problem
with the queue as such.

[emi...@gmail.com]

[...]

>
> > this command (ENABLE AUTOSTART /QUEUES ) is in one of the file processed
>
> > during system startup (at least I hope so)
>
>
>
> Verify!

is there a way to record in a text file all the messages that are displayed during system start?

can you tell me which system files (at least the most important) one by one is VMS processing during boot?

>
>
>
>
>
> Systartup_vms.com is most certenly processed. But the enable autostart
>
> command might not be. There might some logic in the startup that
>
> prevents it from been executed, or something else is not in the
>
> correct state when it is executed. One need the output from
>
> a clean boot to tell wht is happening.
>
>

How to record the output?

>
>
> So ENABLE AUTOSTART /QUEUES seems to have fixed the problem
>
> with the queue as such.

yes but seams it was not the only problem because my problems remain: no connection to the CMM nor at least the printer

Wojtek

[Jan-Erik Soderholm]

emi...@gmail.com wrote 2013-04-23 14:23:
> [...]
>>
>>> this command (ENABLE AUTOSTART /QUEUES ) is in one of the file
>>> processed
>>
>>> during system startup (at least I hope so)
>>
>>
>>
>> Verify!
>
>
> is there a way to record in a text file all the messages that are
> displayed during system start?
>

I think there is some system parameter that can be set to
get a file with the boot output. I usualy connect a terminal
emulator (PuTTY or whatever) to the serial console port
and log everything to a file. That way one get the full
startup including power-on self-test and everything.

> can you tell me which system files (at least the most important) one by
> one is VMS processing during boot?
>

There are a couple that VMS runs, but in most cases it's
enough to look at systartup_vms.com and any files called
from that one.

>>
>> So ENABLE AUTOSTART /QUEUES seems to have fixed the problem
>>
>> with the queue as such.
>
> yes but seams it was not the only problem because my problems remain: no
> connection to the CMM nor at least the printer
>

Right. *That* solved the problem with the stopped *batch* queue !

I'm sure that you have some *other* queue that is setup
against the actual printer. You have to check the system.

What LAT-port is the printer using?
What queue is setup aganst that LAT-port?
Is the queue running?

And so on...

*OR*, get some help !

Jan-Erik.

> Wojtek
>

[Stephen Hoffman]

On 2013-04-23 11:13:26 +0000, emi...@gmail.com said:

> As said, I'm newbe with the VMS - my knowledge does not go too far
> from: dir, type, set def , show.

As I tell all the folks that are making that claim, um, so what?

We were all newbies to VMS once.

Want to be less of a newbie?

Please read the available OpenVMS manuals. Most of the OpenVMS-related
product documentation is here <http://www.hp.com/go/openvms/doc>, and
you'll want to click on the link to the OpenVMS operating system
documentation for that documentation.

To make effective use of OpenVMS, you really need to read through the
OpenVMS User's Manual, and then — depending on what you're planning to
do — read either or both of the OpenVMS Programming Concepts manuals
and the OpenVMS System Managers' manuals. These documents are the
foundation of the rest of the documentation, and more importantly of
knowing how to use, program, and manage OpenVMS systems.

With that knowledge, you will have a far better idea of the terms and
concepts and commands, and the programming constructs and APIs and
related.

OpenVMS is from an era when there were detailed manuals, and from an
era when there really needed to be these sorts of documents provided.
Yes, it's a pain to skim all that text, but that text is free to read,
and the PDFs can be downloaded into your preferred ebook reader, etc.

Some familiarity with the documentation will help you get answers to
your questions more quickly, too.

If you're in a particular hurry to get this stuff working and back
online, then you're likely going to need to connect with somebody
that's already read through the manuals and that has had some
experience with troubleshooting complex configurations.

[abrsvc]

This is being worked directly/offline with progress being made. In order to keep things somewhat secure, only the more generic issues will be posted.

Dan

[David Froble]

Stephen Hoffman wrote:

> OpenVMS is from an era when there were detailed manuals, and from an era
> when there really needed to be these sorts of documents provided.

My question is, "when did this change?"

[Stephen Hoffman]

As computers became available outside of the glass temples and the
glass rooms, and became increasingly common in branch offices, homes,
closets, and pockets.

For advanced management and for programming, you can still need
experienced staff and the modern analogs of the wall of manuals.

For getting newer boxes useful for common tasks (and which can involve
some programming tasks), the manuals are much thinner.

I've previously posted on the User Interface topic.

[dan.gi...@telia.com]

Den torsdagen den 18:e april 2013 kl. 16:38:19 UTC+2 skrev emi...@gmail.com:
> Hi All,
>
> I have a problem with communication between the DEC coomputer and our CMM (coordinate measuring machine: B&S PFx MicroXcel, to be specific) and I was hoping that someone could help me a little to test if the problem is in DEC3000 + DECServer90TL or is it inside the CMM control unit. I have to mention that I do not know much about the VMS, just very basic stuff.
>
>
>
> The machine is operated by the software called Quindos. The CMM is connected to port 1 of the DECServer90TL and DECServer connects to the DEC3000 through CentreCOM MR122T Micro repeater.
>
>
>
> When starting Quindos we get an error message that it can not connect to the CMM just like the CMM was not powered on - but it is.
>
>
>
> I need to know if the DEC3000+DECServer configuration etc. is ok before we call for the CMM service because they are able to check only if the CMM comuter is ok, they do not know anything about DEC and OpenVMS 6. So if it's in DEC it will be money waste, and they are expensive.
>
>
>
> Here is what I already was able to check:
>
> - I do not see any error messages during DEC start up on the screen,
>
> - the DECServer90TL device seems to download the necessary software from the DEC3000 correctly because the 3 diodes (on the left side) are lit as written in the manual which means that it communicates with the computer correctly, downloaded a software from DEC and is ready for operation (but none of the 8 port diodes is lit),
>
> - in VMS I was able to connect to the DecServer device (through the commands: mcr ncp) and check the parameters of the ports (I used the info given on this site: http://www3.sympatico.ca/n.rieck/docs/openvms_notes_decserver_lat.html)
>
> to which the CMM and the printer (LA75, port 5) is connected; and it seems that the parameters are set correctly as specified in the QDS_TERMSET.COM file, i.e. for the CMM port: 7bits, parity=even, speed = 4800 (in both directions) and for the printer port: 8bits, parity =none, speed = 9600 (both directions).
>
> - I tried to print something but without success. No mater from where I try to print (i.e. NCP - "test port 5" command, VMS - "print" command, QUINDOS) the printer (LA75) does not respond and the "DEC" diode blinks all the time on the printer (in Quindos: command "Connect printer" lits the port 5 diode on the DecServer device but nothing happens after calling print command).
>

> - I checked for the QUEUEs and there is one set: BATCH$LEITZ but it says it's "autostared but stoped" - I do not know about "queues" so do not know what that means, and I have no idea what could be wrong.
>

> - we tried to connect a PC with WinXP to the DECServer ports through RS232 and "listen" on the Hyperterminal software to the ports (setting appropriate transmission parameters) but without any success. On the other hand, we are not sure about the wiring between the RJ45 -> RS323 (9 pins).
>
>
>

> I'm hoping that there is some setting in the VMS lost for "lighting up" the ports.
>
>
>
> Does anyone have any ideas what can I check/test?
>
>
>
> I'd be grateful for any help
>
> regards
>
>
>
> Wojtek
>
>
>
> ps.
>
> I do not know if following could be connected with it but the problems
>
> occurred after a day when we received message "not enough free blocks on disk"
>
> during saving a programme in Quindos. what I did at that time was
>
> "purge" whole disk I think, could I delete some system files with that?
>
> And I could not print at that day also but again: I haven't try to print
>
> before that day neither.

You are mentioning a DEC3000, and therefore it must be Quindos 3.2 or 3.3 running on OVMS 6.1 or higher.
You are also using a CentreCom MR122T, indicating a an RJ45 to coax-cable connection.
It's not always reliable.
You can call a comm.-program called APX directly from the QDS-prompt (i the DEC-term), before executing Quindos.
Select to connect to CM (Coordinate-machine).
If the response is "READY" there is a working RS232-connection to a Sharpe 32Z , talking the Leitz -protocol, most likley through LTA104.
You can also use the command CMTTCO, directly from Quindos, (CM to TeleType COntrol) to do the same check (leave with %-sign).
"Not enough free blocks" is not an issue at this stage of the testing, its rather a question of the DECserver or the microportrepeater if the tests above is not positive.

QUINDOS, the best CMM-software available :-)
// Dan

[emi...@gmail.com]

[...]

>
>
> You are mentioning a DEC3000, and therefore it must be Quindos 3.2 or 3.3 running on OVMS 6.1 or higher.
>

Hi Dan and yes - Q3.3 and OVMS 6.1 or 2 not sure now

> You are also using a CentreCom MR122T, indicating a an RJ45 to coax-cable connection.
>
> It's not always reliable.
>
> You can call a comm.-program called APX directly from the QDS-prompt (i the DEC-term), before executing Quindos.
>
> Select to connect to CM (Coordinate-machine).
>
> If the response is "READY" there is a working RS232-connection to a Sharpe 32Z , talking the Leitz -protocol, most likley through LTA104.
>

I get error no such device - CMM is started it's B&S MicroXcel PFx 765 and the controller is Sharpe32 (I'm not sure of the Z), connected to LTA101:

QDS>apx

VAX APXLOD/TERMINAL UTILITY C 2.5

Channel Name (C=CM:, T=TV:) : c

%SYSTEM-W-NOSUCHDEV, no such device available

> You can also use the command CMTTCO, directly from Quindos, (CM to TeleType COntrol) to do the same check (leave with %-sign).
>
> "Not enough free blocks" is not an issue at this stage of the testing, its rather a question of the DECserver or the microportrepeater if the tests above is not positive.
>

Dan, I was also thinking about reseting the DecServer90 but we were told in the past not to do it because it will loose some settings, so I'm afraid. Do you think the reset could cause more problems? Now I'm able to login to the DecServer and check the ports configuration but there must be a way to light up the diodes of the particular port or are the diodes just reacting on the signals sent?

Wojtek
emilwp gmail.com
Wojtek

[Scott Dorsey]

I think the primary milestone was the Macintosh, which came with a
quarter-inch thick brochure and no programming interface in the default
configuration. It was the first computer sold as an appliance rather than
as a programming environment.
--scott

--
"C'est un Nagra. C'est suisse, et tres, tres precis."

[Jan-Erik Soderholm]

pem...@gmail.com wrote 2013-04-24 13:08:

> I get error no such device - CMM is started it's B&S MicroXcel PFx 765
> and the controller is Sharpe32 (I'm not sure of the Z), connected to
> LTA101:
>
> QDS>apx
>
> VAX APXLOD/TERMINAL UTILITY C 2.5
>
> Channel Name (C=CM:, T=TV:) : c
>
> %SYSTEM-W-NOSUCHDEV, no such device available
>

Or in other words, device LTA101: does not exist.
What does "$ SHOW DEVICE LTA101:" says ?
I guess you get the same error message, not ?

Or "$ SHOW DEVIVE LTA" to list all LTAnnn devices.

This is a *local* error in VMS and has nothing at all
to do with any DECServer or anything else outside of
the VMS system.

You must then begin with finding the

$ LCP CREATE PORT ...

or maybe

$ MC LATCP CREATE PORTu

command in your system startup scripts. I'd do :

$ SEA SYS$STARTUP:*.COM LTA101

to track down the place where the LTA101 is created.

Then find out why this wasn't created at last startup....

>
> Dan, I was also thinking about reseting the DecServer90 but we were told
> in the past not to do it because it will loose some settings, so I'm
> afraid. Do you think the reset could cause more problems?

What does "reset" mean in this case ?

A simple poser off/on? Should be safe, as long as all settings
was done with both SET (in RAM) *and* DEFINE (in EEPROM/flash).

A factory reset? You will have to setup everything from scratch.
This can be as simple as saving the SHOW PORT output and
use that as template for SET/DEF commands.

Or simply RTFM for your system and application!

Why on earth are you not getting someone to help you?

Jan-Erik.

[dan.gi...@telia.com]

As I recall, there should be some logicals defined :
CM (Coordinate Machine)
LP (Line Printer)
PL (Plotter)
DI (Digitizer)
VM (Virtual Machine)

By default LTA104, 105, 106 and 107 was used on B&S, DEA and Leitz CMM's.

SH LOG CM should point at LTAxxx (by default it was LTA104)
If CM exists, then the controller could be a Sharpe32 Z.

If not, do the same check on VM (SH LOG VM, could also be a symbol, SH SYM VM)
If VM exists, then it's a regular Sharpe32-controller, talking the Sharpe-protocol, which differs a lot from the Leitz-protocol.

In case of a Sharpe32, then Quindos starts a driver (XCL_110.EXE) that acts like an interpretator between Quindos and the controller,

I think that XCL_110.EXE can be found in QDS_MANAGER (DIR QDS_MANAGER)

But, first of all, it must be some LTA-devices.
It's also possible that the TTAx-/TTBx-devices have been used.

It is possible to "trace" what DCL-procedures are called upon login.
Begin with SYS$LOGIN:LOGIN.COM and follow and check each line.
Also follow all the calls that points to QDS_MANAGER, QDS_SYSTEM, .......

Pls bare in mind that it was many years ago since the last time I installed and configured a CMM like the one You are struggeling with.
// Dan

[emi...@gmail.com]

Dear Dan.gi..@talia.com and All,
I'm still strugling with the lack of communication CMM-DEC3000.
I have had traced the calls in the startup files. I took me quite time because I was discovering "the wheels" on VMS. That's why I haven't wrote for such long time.

It seems that all ports and logicals (VM, PL) etc. are defined when the Quindos is started (e.g. the VM as LTA101: in QDS_ASSDEV.COM located in the QDSCMM folder or deeper) and from the software side everything is fine.

Is there a possibility that the communication signal is blocked by lack of priviliges or somthing like that? I'll try to explain what I mean:
1. DECServer is selftesting and says it's ok,
2. the ports (LTA*) are defined and I can connect to the device check the ports' settings are ok etc.
3. the logical names which are necessary for the Quindos software (VM, LP) are defined during the software startup.
4. issuing printing command from the Quindos causes the diodes on DECServer to blink and light in a correct way
BUT
5. no signal is comming out from the ports
can this be blocked by the system (some PROTECTION settings or so)? how can I check it?


Now strictly QUINDOS specific:
I found 2 files which contain the history of the communication commands between the Quindos and the CMM since 1995! first file is "Quindos.log" and e.g. from the day the problems started I copied following lines:

# 11:18:56.95 I$I ALLOPN USER 15-JAN-2013
# 11:18:57.02 I$I ALLOPN USER QUINDOS PFX
# 11:18:57.04 I$0 ALLOPN STARTING QUINDOS-V 3.30-#364
# 11:18:58.68 I$1 LDBOPN LDBOPN$1
# 11:19:00.87 I$2 ALLOPN GDBOPN$2
# 11:19:38.06 I_3 CTRVER$3 _XCL25 Waiting for machine start
# 11:19:44.62 S_1 GTER15$1 _XCL15
# 11:19:45.86 S$2 CREVCM CREVCM$2
# 11:20:23.92 S_2 PRBHTY$2 _XCL03
# 11:20:27.03 I$9 LMGINI LICRQS$9 PFXDRV
# 11:20:28.49 I$7 LMGINI LEITZ:: 68585E9D
# 11:20:28.58 I$1 ALLOPN NO$NAME
# 11:20:59.81 W_1 QIOWTO QIOWTO
# 11:22:52.81 I$I ALLOPN USER 15-JAN-2013
# 11:22:52.88 I$I ALLOPN USER QUINDOS PFX
# 11:22:52.88 I$0 ALLOPN STARTING QUINDOS-V 3.30-#364
# 11:22:57.84 I$1 FILOPN BADHDR$1 QUINDOS.GDB
# 11:22:57.90 I$2 FILOPN BADSIZ$1 QUINDOS.LDB
# 11:22:58.26 I$1 LDBOPN LDBOPN$1
# 11:22:58.32 I$1 FILOPN BADHDR$1 QUINDOS.GDB
# 11:22:58.58 I$1 FILOPN STARTR QUINDOS.GDB
# 11:22:59.90 I$2 FILOPN CPYDBS QUINDOS.GDB
# 11:23:00.00 I$2 ALLOPN GDBOPN$2
# 11:25:33.46 S$1 CMABRT CMABRT$1 Process deleted !
# 11:25:34.35 S$2 CREVCM CREVCM$2
# 11:25:44.87 I$1 ALLOPN NO$NAME
# 11:25:44.87 I$9 LMGINI LICRQS$9 PFXRMT
# 11:25:46.55 I$7 LMGINI LEITZ:: PFXRMT 87DF1463
# 11:28:30.61 S$1 CMABRT CMABRT$1 Process deleted !
# 11:28:31.30 S$2 CREVCM CREVCM$2
# 11:28:50.78 I$3 QUINDOS LOGOUT QUINDOS

the line:
# 11:25:33.46 S$1 CMABRT CMABRT$1 Process deleted !
is the problem

another file "QUINDOS.CML" is much bigger, over 144000 blocks and there are more detailed commands - a few lines for each second. Dan, do you think there could be some hints on what can be wrong?

Dan, I hope you will read it and get back to me

regards
Wojtek
emilwp()gmail.com