What level of compilers is required for CATIA and Catgeo development? |
|
|
A. When mixing aCC 1.07 and higher code delivered by Dassault Systèmes, you may have the following message when running some applications:
/usr/lib/aCC/dld.sl: Unresolved symbol: $global$ (data) from $CATIA/code/steplib/libJS03TRA.sl ... Relink your application by adding the compiler option "-Wl,-E" to the aCC line in order to export all the symbols - including the exclusive $global$ symbol -. These options indicate to the linker that all the symbols must be exported.
If you are using the 'ld' link command, just use the "-E" option to export all the symbols.
To know the level of compiler and builder your system has been setup with, execute the following commands:
what /usr/lib/libCsup.1
/usr/lib/libCsup.1:
HP aC++ B3910B A.01.21 Language Support Library
(PHSS_17872 / aCC runtime libraries A.01.21)
what /opt/aCC/bin/aCC
/opt/aCC/bin/aCC:
HP aC++ B3910B A.01.21
HP aC++ B3910B A.01.19.02 Language Support Library
what /opt/ansic/bin/cc
HP92435-01 A.10.32.03 HP C compiler
what /opt/fortran/bin/f77
HP-UX f77 960522 (095222) B3906AA/B3908AA B.10.20.01
what /usr/bin/ld
/usr/bin/ld:
92453-07 linker linker ld B.10.37 991028
(PHSS_21110 / ld(1) cumulative patch)
|
|
How do I create a R/O Asian environment for CATIA? |
|
|
A. You need to apply the R/O Asian bundle that includes the required character sets to read CATIA models containing Asian characters. Please refer to Asian R/O Environment for CATIA for information on how to configure your system.
|
|
How do I set up LUM and iFOR/LS setup for CATIA V4 and V5? |
|
|
A. Please refer to Licensing with LUM. Note that starting from LUM 466, the APA (Auto Port Aggregation) environment will be supported.
|
|
How do I start the CATIA V422 Documentation on HP-UX? |
|
|
A. When launching 'StartDOC' from the CD, the 'fmarch' script is executed to determine the type of the system you are using. This procedure calls the 'uname' function from the '/bin/' directory. However, 'uname' is located under '/usr/bin' and not '/bin'.
If you have downloaded the documentation onto your system, just modify the 'fmarch' script. Otherwise, create a symbolic link under '/bin' to access the 'uname' function (ln -s /usr/bin/uname /bin/uname).
|
|
How do I switch the rotation mode in V4 when running an Asian environment? |
|
|
A. After changing UNSPEC-ROT by F3 key, releasing F3 key doesn't stop changing mode. This is due to the language patches used in ACE5. Please refer to Asian R/O Environment for CATIA on HP-UX for information on installing the R/O Asian patch bundle.
|
|
What level of HP compilers is required for GII applications? |
|
|
A. On a HP-UX 10.20 system, you need to install:
* B3907CA: HP FORTRAN/S700 Compiler and its associated products
* B3899BA: HP C/ANSI C Developer's bundle for HP-UX 10.20 (S700)
* B3911DB: HP aC++ Compiler S700.
Please refer to the first question above to get the appropriate level of the compilers.
|
|
Why does CATIA V4 generate an error when converting a model into DFX/DWG format? |
|
|
A. The problem appears first in CATIA 422R1. Previous releases of CATIA work fine. Before starting CATIA, do an export PDELIB_TMP=/tmp where /tmp has sufficient free disk space. This is a temporary space required by CATIA for its (internal) I/O whatever the platform used. At the end of a successful execution CATIA will delete all its temporary files. Another location with sufficient space can be specified instead of /tmp. If you attempt to convert models containing DBCS characters, pls note that there is a defect reported in APAR HD05582 (CATDXF: DBCS CHARACTERS ARE NOT CORRECTLY TRANSLATED WITH HP-UX) fixed by applying the UH03414 Ptf.
|
|
What causes the "libgeo too large" message when developing a V4 application? |
|
|
A. Due to the large size of the libgeo library, you may have troubles when trying to load this lib and then some symbols cannot be found. So you might try the two following options to fix the issue: - split the libgeo.a into 3 (or more) shared libraries in order to reduce the number of symbols to be exported. To do so: mkdir /tmp/libs
cd /tmp/libs
ar x libgeo.a
ld -b -o libgeo1.sl [a-e]*.o
ld -b -o libgeo2.sl [f-l]*.o
ld -b -o libgeo3.sl [m-z]*.o
Then modify the 'makefile' to take into account this modification.
- Make sure to mention explicitly the GGGG50.o symbol prior to the shared libraries in the link command.
* Sample of Makefile:
dcg -F sample \
-p *.o \
/tmp/libs/lib/GGGG50.o \
/tmp/libs/libgeo1.sl \
/tmp/libs/libgeo2.sl \
/tmp/libs/libgeo3.sl \
-o /tmp/libs/SAMPLE ;
cp /tmp/libs/SAMPLE/home/adm423r1/code/steplib/HP-UX; |
|
|
Why does VPM fail the first time it is launched? |
|
|
A. VPM 1 generates a X/Motif related abend when starting the first time on HP-UX. This is a well-known issue from Dassault Systèmes due to the licensing management. Dassault Systèmes has implemented a workaround which consists into starting the license process (catlicsr) before launching the VPM executable. Edit the '<vpmadm>/code/bin/PMStart.sh' script and search for the 'sleep' string. Depending of the configuration you're running, you might have to modify the sleeping time. Default is 5 seconds.
|
|
How do I fix the bad colormap allocation when starting CATIA V4? |
|
|
A. Check the value of the DISPLAY shell variable. By default, the variable is set to local:0.0 which causes troubles in the color allocation process. Make sure to export the variable to `hostname`:0.0. In addition to that, a color allocation issue may occur when starting DMU V5 (dmustart) first and then CATIA V4. It appears that CATIA V4 uses a very simple minded color allocation scheme, and does not know how to handle it if colors are not available. It looks like that DMU allocates colors out of the default colormap if enough are available (which there are if it starts first). If there are not enough (as in the case when V4 is running) it somehow handles it. The DMU application is very strange and seems to be behaving badly. All of the windows sound to be depth 24 TrueColor (even if the default visual is depth 8 Pseudocolor) and have their own private colormap (use xwininfo to get a window report). But, DMU apparently allocates a very large number of private colors(almost 200!), which it does not appear to use, but keeps other apps from using. CATIA V4, on the other hand, looks like it only tries to get 10 or so private colors.
One workaround is to set the Default Visual to Depth 24 TrueColor (DirectColor works fine only on fx family). Use the xdpyinfo utility to check the parameters for the windows. SAM can be used to modify the X0screens file (for fx family) and the XF86Config file (for FGL-UX) and set the DefaultVisual to TrueColor Depth24 without any performance penalties as result.
However, for FGL-UX only, you have to manually edit the XF86Config file and add the following line in the "Device" section:
Option "DefaultVisualTrueColor" "true"
Then restart the Xserver (Ctrl+Shift+Break) to make the modification effective in the next login session, and check also the X configuration with the xdpyinfo utility. Make sure the Default Visual is set to TrueColor Depth 24.
|
|
Why does HP-UX hang when starting the N4D product? |
|
|
A. The Xserver freezes when the N4D 'splash' window is displayed. Make sure the Xserver patch from September '01 has been installed on the system. Ref is PHSS_23566. Please refer to the HP-UX graphics page to get more detailed information.
|
|
Why is the libf.sl library missing on HP-UX 11.xx? Does CATIA V4 require this library? |
|
|
A. The libf.sl library is part of the fortran package. It's no longer delivered with HP11 and it has been replaced by the libcl.1. If the application is looking for this library, you can create a symbolic link between the /usr/lib/libcl.1 and the /usr/lib/libf.sl. This error can occur in CATIA V4 Auxview2 function or in the IGES translator.
|
|
How do I make the Alt<Key>Up key-sequence work in V4? |
|
|
A. With CATIA V4 running on HP-UX 11, it's no longer possible to pick a rotation axis and then by hitting the Alt<Key>Up or Down arrows rotate the part around the axis. The origin of the problem is that the Alt<Key>Up sequence has been overwritten. Execute the following steps to turn around: - Copy the /usr/dt/config/C/sys.dtwmrc file to the /etc/dt/config/C directory. This is to ensure that you do not overwrite the system-default configuration of the system and modifications to files in the /usr/ directory may be overwritten in subsequent patching to the system.
- Comment out the Alt<Key>Down and Alt<Key>Up lines under the "Key Bindings Description" section.
- Although restarting the workspace manager should force these modifications to be recognized, you may want to log out and log back in to ensure that the previous settings are not loaded into the cache of the system.
|
|
|
Why are double-byte characters displayed wrong? |
|
|
A. If you get bad characters (like 4!5!) in the character field with the KANJ font, then apply the following workaround:
Edit "$CATIA/adm/xfont/fonts.alias" file as below:
CATIA.font.japan.sbcs -hp-gothic-medium-r-normal--18-180-75-75-c-80-hp-japanese15
CATIA.font.japan.sbcs -hp-gothic-medium-r-normal--18-130-100-100-c-90-jisx0201.1976-0
CATIA.font.japan.dbcs -hp-gothic-medium-r-normal--18-180-75-75-c-160-jisx0208.1983-0
CATIA.font.japan.dbcs -hp-gothic-medium-r-normal--18-130-100-100-c-180-jisx0208.1983-0
CATIA.font.japan.bold.sbcs -hp-gothic-medium-r-normal--18-180-75-75-c-80-hp-japanese15
CATIA.font.japan.bold.sbcs -hp-gothic-medium-r-normal--18-130-100-100-c-90-jisx0201.1976-0
CATIA.font.japan.bold.dbcs -hp-gothic-medium-r-normal--18-180-75-75-c-160-jisx0208.1983-0
CATIA.font.japan.bold.dbcs -hp-gothic-medium-r-normal--18-130-100-100-c-180-jisx0208.1983-0
|
|
Where does the "cannot exec /usr/lbin/ctco" error come from? |
|
|
A. When running the aCC compiler as catadm, the following error occurs:
aCC: internal error 1901: cannot exec /usr/lbin/ctcom: 2 (No such file or directory)
This pb is probably due to the setting of the PATH variable. To workaround of this, either invoke aCC by absolute path or move up /opt/aCC/bin in the definition of the PATH variable (export PATH=/opt/aCC/bin:$PATH). This is a known issue which has normally been fixed in the 1.27 aCC (and higher level). Do a what /usr/lib/libCsup.1 to get the level of aCC, but based on the certified Dassault Systèmes compilers, you should run a 1.21 aCC.
|
|
Why is it not possible to select wireframe elements in a V4 shaded model? |
|
|
A. Starting from March 2002, selection of wireframe elements in a shaded model is no longer possible. There is a temporary workaround that takes you back to the way it used to work. Do an export HP_USE_SW_PICKING=1 before executing CATIA V4. A fix has been delivered within the June 2002 release.
|
|
How do I remove the "quad4map_32bit: rmap ovflo ..." message when running CATIA or VPM? |
|
|
A. This message can appear in the CATIA launching window, or in /var/adm/syslog.log file or in the 'dmesg' output. The quad4map messages are caused by fragmentation in the 4th quadrant where shared objects are located. Try to increase the "shmmni" KL parameter to an higher value (default is 200) and reboot your system. "shmmni" specifies the maximum number of shared memory segments allowed to exist simultaneously, system-wide. The value cannot exceed 1024.
|
|
Is there a list of tuning rules for the V4 / Auxview2 function? |
|
|
A. Below are some basics to set the CATIA parameters for the Auxview2 function: - Modify the CATIA.MODEL_KBYTES.MAX_ACTIVE_DATA and CATIA.MODEL_KBYTES.MAX_ACTIVE_INDEX parameters to be able to load the 3D models/session and generate the 2D drawings.
- The CATIA.MODEL_KBYTES.TOTAL_OVERLAY_INDEX value specifies the space that Auxview2 will allocate to perform the computation stage. Usually: TOTAL_OVERLAY_INDEX = 2 x S MAX_ACTIVE_INDEX. If dittos or/and sections are part of the computation, you may increase the above value.
- Go to the Erase>Pack function in HLR visualization mode, and check the value of the CATIA.MODEL_KBYTES.GLOBAL_EXTENDED_DATA field which has to be lower than 100%.
- The sum of MAX_ACTIVE_INDEX and TOTAL_OVERLAY_INDEX must be lower than 128MB.
- As the drawing processes consume a lot of memory, please check the PLM Competency Center tuning section to implement the Mallopt feature.
|
|
|
How do I change the PF keys definitions for CATIA V4? |
|
|
A. You can modify the /etc (or /usr) /dt/config/$LANG/sys.dtwmrc file to assign new functions on the different PF keys. CATIA V4 has its own definition in <catadm>/adm/xcfg/Catia.table file. $LANG is also used to manage the DBCS language.
For example:
<Key>F2: peelingwindow
Alt <Key>F2: peelingwindow
<Key>F11: yes()
|
|
How do I fix the aCC runtime error when running CATIGE or IGECAT? |
|
|
A. The "aCC runtime: ERROR: _main() not called" message is being generated by the iges module (TI0IGESP) called by catutil and is the result of tighter error checking by the aC++ support library delivered with patch PHSS_20055 (s700_800 11.x HP aC++ runtime libraries (aCC A.03.25)) and later (PHSS_26945 is the latest one as of June 03). The support library function _main() must be called by all C++ applications to assure that static constructors and destructors are called. If the user-defined function main() is compiled by aCC, this is done automatically. However, if main() is compiled by the C compiler, user code must call _main() explicitly. What you could do is to identify the module that is executed by catutil and do a 'chatr' to list all the dependencies. You should see a CC lib among the list (like libCsup). Do a 'what' on this lib to get the exact level, and this would explain why you get the _main() error message. Anyway, execution of iges should work OK even with the error message.
|
|
Why does CATIA vanish in an NIS environment? |
|
|
A. - Try to start Catia V4 with the following command: catini -XM (without "-cs"). This should bring you an intermediate GUI screen.
- Click on the "COLD START" button, in the upper right corner. You should get that kind of error message in the status bar below:
"getpwuid fails, check /etc/passwd file"
- Check the content of "/etc/passwd" and "/etc/group" files. Add a line at the end of those files beginning by "+": if it isn't already present.
Example:
"/etc/group"
other:...
bin:...
+:
Do the same thing for "/etc/passwd". "/etc/passwd"
root:...
bin:...
+:
|
|
|
How do I specify a startup model in CATIA V4? |
|
|
A. Update the V4 declaratives (DCLS file) to include the following variables :
CATIA.INITIAL_MODEL.READ = TRUE : to activate the model startup feature
CATIA.MODEL = '"/tmp/startup_dir","STARTUP"' and CATIA.INITIAL_MODEL.READ.DLNAME ='STARTUP' : to define the DLNAME of the startup directory
CATIA.INITIAL_MODEL.READ.NAME.SPACE = 'SP startup_model' : to specify the 3D model name
CATIA.INITIAL_MODEL.READ.NAME.DRAW = 'DR startup_model' : to specify the DR model name
Complementary information can be found in the "V4 Declaratives quick reference guide" documentation.
|
|
|
Printable version
