Hello Pedro:
Please show us the output of these commands:
as -V
cobmode
cob -vD -x tictac.cbl
as -V shows the version of the system assembler.
cobmode shows the current active mode for the COBOL system: 32 or 64
The -vD option will make cob more verbose and tell us what cob is doing behind the scenes.
Dear Dan,
Following the result for your question :
as -V
as: not found
# cob -vD -x tictac.cbl
cob64 -C nolist -CC -KPIC -A -KPIC -N PIC -vD -x tictac.cbl
/opt/microfocus/cobol/bin/cobchecker64 tictac.cbl int("tictac.int") anim csi verbose nolist
* Micro Focus Server Express V5.1 revision 000 Compiler
* Copyright (C) Micro Focus IP Development Limited 1984-2012.
* Accepted - verbose
* Accepted - nolist
* Compiling tictac.cbl
* Total Messages: 0
* Data: 2400 Code: 2076
/opt/microfocus/cobol/bin/ncg64 tictac.int obj(tictac.o) verbose PIC
* Micro Focus Server Express V5.1.00 Code Generator
* Copyright (C) Micro Focus IP Development Limited 1984-2012.
* Accepted - verbose
* Accepted - PIC
* Generating tictac
* Data: 2192 Code: 3556 Literals: 344 Dynamic: 671744
Entry points defined in module: tictac.o
*TICTAC
tictac
as -K PIC -xarch=v9 -o /var/tmp/cobAAA4CaOJi/%cob0.o /var/tmp/cobAAA4CaOJi/%cob0.s
cob64: can not execute program "as".
Cannot execute system assembler "as". To resolve this, ensure that assembler
is installed, and that this location is on PATH, typically /usr/bin or
/usr/ccs/bin.
cob64: error(s) in assembling /var/tmp/cobAAA4CaOJi/%cob0.s
# cobmode
Effective Default Working Mode: 64 bit
Regrads,
Pedro Juan Montero Bernales
PJM Informatica Soluciones Globales
Av. Ricardo Lyon 2034 Oficina 603
Providencia- Santiago - Chile
( Telefono: (+56-2) 2415-1583
ÈMóvil : (+56-9)7637-8488
e-mail :pjminformatica1@gmail.com
Dera Dan,
Path were As is in our Sun Solaris :
/usr/lib/gnome-private/share/locale/as
/usr/ccs/bin/as
/usr/sfw/libexec/gcc/sparc-sun-solaris2.10/3.4.3/as
/usr/sfw/sparc-sun-solaris2.10/bin/as
/.SUNWnative/usr/bin/as
/.SUNWnative/usr/share/locale/as
Many Thaks,
PJM
I recommend /usr/ccs/bin/as
Put /usr/ccs/bin early on PATH and try again to compile
Dear Dan,
I Try to do this in any way and no work. Please see my profile maybe something is wrong...
MAIL=/usr/mail/${LOGNAME:?}
# variables de ambiente
COBDIR=/opt/microfocus/cobol
AS=usr/ccs/bin/as:$PATH
LD_LIBRARY_PATH=$COBDIR/lib:$LD_LIBRARY_PATH
PATH=$COBDIR/bin,/usr/ccs/bin/as:$PATH
export COBDIR LD_LIBRARY_PATH AS PATH
Your PATH appears to have a "," in it instead of ":"
Dear Chris,
I corrected it and give the same result...
MAIL=/usr/mail/${LOGNAME:?}
# variables de ambiente
COBDIR=/opt/microfocus/cobol
AS=usr/ccs/bin/as:$PATH
LD_LIBRARY_PATH=$COBDIR/lib:$LD_LIBRARY_PATH
PATH=/$COBDIR/bin:$PATH
export COBDIR LD_LIBRARY_PATH AS PATH
Dear Sir,
I was testing Server Express 5.1 and I get the following Error :
error(s) in assembling /var/tmp/cobAAAYmaCRb/%cob0.s when put cob64 -x tictac.cbl
All other command compile work fine.
TKS
PJM
Hello Pedro:
Do not set:
AS=usr/ccs/bin/as:$PATH
instead set:
PATH=/usr/ccs/bin:$PATH
that is, put /usr/ccs/bin early on PATH so the assembler "as" can be found.
Afterwords, verify that "as" can be found by entering:
type as
You could see a result like this:
as is /usr/ccs/bin/as
Hello Pedro:
The documentation, in the section COBSQL Directives, says the option CSTOP or CSP is not available on UNIX. This is why csp was rejected. The documentation says: "you can emulate the CSTOP functionality by installing a closedown procedure that performs an EXEC SQL ROLLBACK ..." See the Server Express documentation for more information.
The directive CSQLT=syb should be specified with two = characters, like this:
CSQLT==syb
If that does not work, try CSQLT==sybase
The directive 'cobsqlinclude' is not documented as a valid COBSQL directive, that is why it is rejected.
Dear Dan,
So sorry I was Reading an Old Documentation. With the new Directivas :
* Micro Focus Server Express V5.1 revision 000 Compiler
* Copyright (C) Micro Focus IP Development Limited 1984-2012.
* Accepted - verbose* Accepted - nolist
* Accepted - p(cobsql) csqlt=syb makesyn
* Accepted - list()
* Micro Focus Cobsql Integrated Preprocessor
* Compiling PrestMedical.pco
* CSQL-I-004: Accepted csqlt=syb
* CSQL-I-004: Accepted makesyn
* CSQL-I-006: Rejected
* CSQL-I-018: Invoking Sybase Precompiler/Translator
sh: cobpre: not found
* CSQL-F-016: UNIX error Return Code is 0001
* CSQL-F-021: Precompiler did not complete -- Terminating
cob64: error(s) in compilation: PrestMedical.pco
$
We are having problems to obtain the Sybase Preprocessor "cobpre". Could you say me were I can get this ???
Hello Pedro:
You can get the Sybase preprocessor from Sybase. I searched the internet. Sybase is now part of SAP.
Dear Sir,
I execute this and get an Error, Could you please what was wrong ..???
$ cob -a -v -P -k PrestMedical.pco -C"p(cobsql) nocst csp CSQLT=syb
cobsqlinclude=/usr/sybase/include">
cob64 -C nolist -CC -KPIC -A -KPIC -N PIC -a -v -P -k PrestMedical.pco -Cp(cobsql) nocst csp CSQLT=syb
cobsqlinclude=/usr/sybase/include
* Micro Focus Server Express V5.1 revision 000 Compiler
* Copyright (C) Micro Focus IP Development Limited 1984-2012.
* Accepted - verbose
* Accepted - nolist
* Accepted - p(cobsql) nocst csp CSQLT(syb
) cobsqlinclude(/usr/sybase/include)
* Accepted - list("PrestMedical.lst")
* Micro Focus Cobsql Integrated Preprocessor
* Compiling PrestMedical.pco
* CSQL-I-004: Accepted nocst
* CSQL-I-006: Rejected csp
* CSQL-I-006: Rejected CSQLT(syb
)
* CSQL-I-006: Rejected cobsqlinclude(/usr/sybase/include)
* CSQL-I-003: COBSQLTYPE is incorrect defaulting to ORACLE8
* CSQL-I-018: Invoking Oracle Precompiler/Translator
sh: procob: not found
* CSQL-F-016: UNIX error Return Code is 0001
cob64: error(s) in compilation: PrestMedical.pco
Please Help me to i
Dear Dan,
Precompilation Successful. No Errors or Warnings found.
Statistical Report:
Program name: cobpre
Options specified:
Input file name: PrestMedical.pco
Listing file name:
Target file name: PrestMedical.cbl
ISQL file name:
Tag ID specified:
Compiler used: mf_word
Open Client version: CS-VERSION-150
Number of information messages: 11
Number of warning messages: 0
Number of error messages: 0
Number of SQL statements parsed: 13
Number of host variables declared: 89
Number of SQL cursors declared: 1
Number of dynamic SQL statements: 0
Number of stored Procedures generated: 1
Connection(s) information:
User id:
Server:
Database:
It will be difficult to provide any assistance without at least basic information. What product is the customer using? What is the Fileshare / FHREDIR configuration?
It would be best to open a Support Incident to track the issue.
I will note that, for Fileshare on Windows, the two simplest ways to improve performance are to:
1. Configure the Fileshare server for synchronous communications mode (using the /sc switch in the Fileshare server configuration file). See the topic "Fileshare Server Configuration Options" in the product documentation.
2. Since this is Windows, if the client and server are running on the same machine, configure the server and client to use CCISM (Shared Memory). Again, refer to the documentation for configuring Fileshare.
I can send you the "cobopt.cfg" and the "MFEXTMAP.DAT"...
COBOPT:
set environment_mapper=TRUE
MFEXTMAP:
...
ankox K:\TestK\Data\anko.dat
...
Hi Bernd,
I think that you have your terminologies confused here. Fileshare is a server based version of the file handler which runs as a separate process on a network server machine. Your program running on a client machine will redirect its file I-O across the network to the fileshare server where the I-O will actually be done.
This is turned on with the directive CALLFH"FHREDIR".
You are specifying CALLFH"EXTFH" which is the default to use the local file handler. The FILESHARE directive that you are using has nothing to do with the fileshare server technology to which Michael is referring but instead simply causes the file handler to treat the files as though AUTOMATIC locking was turned on.
So you are running the program locally and trying to share files on a network drive. The normal cause of performance problems in this environment is caused by the opportunistic locking done by Windows between a client OS and a Server OS.
There is an article from a 3rd party vendor here which although doesn't reference COBOL specifically does explain the problem. If you must share files on a network drive then you should turn off the local caching and oplocks.
In this situation it is often recommended that you do use the Fileshare technology mentioned above to avoid this problem altogether.
Thanks
Hi!
One of my customer is using Fileshare under Windows 7 and Windows 2012 Server and have big Problems with the fileshare System..
Under Windows XP and Windows 2003 there where no Speed Problems...
The Compiler Directives that he is using was:
FILESHARE CALLFH "EXTFH"
In the cobopt.cfg is standing:
set environment_mapper=TRUE
Have anyone a hint for me to bring up the Speed for the programs?
Here an select Cobol sample:
SELECT TITEL
ASSIGN external TITELX
ACCESS DYNAMIC
RECORD KEY TI00
ALTERNATE RECORD KEY ti900 duplicates
ORGANIZATION INDEXED
LOCK MODE MANUAL
FILE STATUS STTITEL.
...
And the FD:
FD TITEL
DATA RECORD RTITEL.
*
01 RTITEL.
02 TI00.
* * MASTER KEY
05 TI000 PIC 999.
I hope anyone can help me and my customer!?
Best Regards
Bernd
Hello, I have some licensing questions regarding Net Express 5.1 if anyone with knowledge on this product can help me:
1. In case you have a CPU based license how do you determine the required number of CPU licenses if Net Express 5.1 is deployed on a virtual server (e.g. VMware) ?
2. Do you count the number of virtual CPU's, physical CPU's, physical cores?
3. What if the virtual server is part of a VMware cluster?