question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
---|---|
Problem Statement: The Set RUTIL does not show up in the set catalog window. | Solution: Set your ULEVEL to the max which is 4 and then go to the catalog window and look for RUTIL. RUTIL security level is set to 3 by default and maybe your ULEVEL is set to a lower number than 3. To check your ULEVEL on the Command line in MIMI type ULEVEL and see what number it is set to. To change it, type ULEVEL 4 on the command line in MIMI and this sets it to the maximum.
KeyWords
Keywords: None
References: None |
Problem Statement: When a user attempts to open a case file, they may receive the following error message:
"Cannot Execute: Call Chesapeake for replacement" | Solution: This error message indicates that the user must contact MIMI support and request a new installation code for their system. The user should generate their system code and send it to [email protected]. MIMI support will generate the new installation code, which the user installs on their system.
This should fix the problem and the user should be able to open case files without any further error messages.
KeyWords
error message
can not execute
case file opening
Keywords: None
References: None |
Problem Statement: How to use the User Modifiable Planning Board parameter (UMPB) | Solution: One of our customers recently faced a problem with an activity (a truck loading operation) mistakenly moved on the Planning Board.
This incorrect manipulation led the entire process of dispatching the schedule information to be erroneous.
It eventually ended with some timing problem with trucks waiting at the loading pipe of the refinery...
There is a useful parameter in the Planning Board Control table (CNTLS) that can be used to avoid such an issue.
The User Modifiable Planning Board (UMPB) parameter allows a user to de-activate some functionalities of the Planning Board to prevent the modification or rescheduling of activities by using the Activity Editor or the Drag and Drop feature.
Those are:
Create Activity
Duplicate Selected Activity
Split Activity
Combine Activity
Move Activity
Delete Activity
If it does not exist, the UMPB parameter can be added to the CNTLS table and can be set to NO or YES accordingly.
Close and re-open the Planning Board for the new CNTLS(UMPB) setting to take effect.
Additional information can be found in the MIMI Online Help tool (Aspen MIMI Scheduling, Planning Board)
KeyWords
UMPB
PLANNING BOARD
ACTIVITY EDITOR
CNTLS
Keywords: None
References: None |
Problem Statement: I am running MIMI and it terminates with a runtime error. | Solution: MIMI is memory intensive and, if you are running other applications in the background, the workstation can run out of memory and consequently will cache to virtual memory. However, if you do not have enough hard drive space on the hard drive that MIMI resides, you can run out of virtual memory and MIMI will terminate.
KeyWords:
Keywords: None
References: None |
Problem Statement: What port does the MIMI broker use? | Solution: The broker uses port 111. The Noblenet Portmapper reserves port 111 for use by the MIMI broker. You can see this by using the portview.exe utility that is in the MIMI\BIN folder.
KeyWords:
Keywords: None
References: None |
Problem Statement: What is the maximum number of entries allowed in a SET or TABLE? | Solution: The maximum number of entries in a set is 10 million.
The maximum number of entries in a table would be equal to the maximum number of set entries * maximum number of set entries.
KeyWords:
Keywords: None
References: None |
Problem Statement: What is the difference between Server install and Standard install of MIMI application? | Solution: At the beginning of the MIMI Installation, the setup program will prompt you to select a type of MIMI installation either Server or Standard install. The Server installation will install the entire MIMI application (about 300 MB) which includes Aspen MIMI Light Client, Aspen MIMI Limited Editor, and Aspen MIMI. If you are using Distributed MIMI, MIMIX, and running a MIMI batch job in the background then you must install using the Server option.
Possible error message that can occur if you where using Standard installation but the Server installation was necessary:
Noble Net Portmapper or MIMI Broker not started
MIMI.exe ERROR message and program will terminate.
Winsoc BRK_Server error
Standard install does not install everything described for the Server install. If you received any errors describe above during installation then you will need to install Server to fix the problem.
The Help Desk recommends to install Server mode because it is better to have the complete package (all the MIMI modules you are licensed to used) installed so when your business model needs to run a specific MIMI module, you already have it. You will not need to uninstall then reinstall MIMI again.
Keywords: None
References: None |
Problem Statement: XPRESS command is returning an error code "8-278: could not initialize" | Solution: Check the tape.inf file in your \MIMI\lib directory and make sure that the file contains an XPRESS license. To do so, look at the 3rd line of this file and make sure that the word "XPRS" is listed.
If step one is true, then the \MIMI\license directory should containa folder called xprsslic which should have two subdirectory files: a. Mp-opt.msg b. Xpress.pwd
If the xprsslic folder is missing, then relicense MIMI and make sure it is pointing to the correct tape.inf that has the XPRESS license.
Call MIMI support for your installation code then make sure the xprsslic folder now exist in the \MIMI\license direcotry.
Test XPRESS command again.
NOTE: Error code 8-278 means that MIMI could not find the XPRESS message files. It also possible that the xpress license has expired and MIMI just needs to be relicensed.
KeyWords
Keywords: None
References: None |
Problem Statement: How do I setup MIMI cases to run automatically and without a user present? | Solution: Two different ways:
Use the GUI version of Windows NT AT Scheduler. This can be obtained in the Windows NT Resource Kit. Use of the GUI is simple and self explanatory. The only thing you have to enter is in the command line, where you will have to manually specify which MIMI case you want to run.
The command line will be (drive letter):\(path)\MIMI\BIN\MIMI.exe (sourcedrive):\ (path of case files)\(casename).cas
If you do not have the GUI version of AT scheduler available, you can still use the DOS version by going to the command line and typying:
AT (time in 24 hour format)/interactive/every:MTWThFSSu (drive letter):\(path) \MIMI\BIN\MIMI.exe (sourcedrive):\(path of case files)\(casename).cas
For more information on the AT command, in Windows click on Start --> Help. Click on the Index tab and look for "at command".
Keywords: None
References: None |
Problem Statement: Is there a square root function in MIMI? | Solution: Mathematical Expressions (like square root) can be defined in MIMI through Non-Linear Functions. Below is an excerpt from the manual:
The following mathematical functions are valid in NLF:
ABS(X): Absolute value of x
EXP(X): Exponential function of x, ex
LOG(X): Natural Logarithm of x
SQRT(X): Square root of x
SIN(X): Sine of x (where x is an angle in degrees)
COS(X): Cosine of x (where x is an angle in degrees)
TAN(X): Tangent of x (where x is an angle in degrees)
ASIN(X): Arc sine of x in degrees
ACOS(X): Arc cosine of x in degrees
ATAN(X): Arc tangent of x in degrees
Rounding functions for tables.
Guidelines for Argument x in Mathematical Functions
x must be a single item - a table name, a table entry, a number, or another NLF function. Example: The following statement is invalid:
TAN(CON1 + 10)
To perform this function, break it into two statements:
NLF1 CON1 + 10
NLF2 TAN(NLF1)
It is invalid to use a unary expression for x. Example: The following statement is invalid:
SQRT(-NLF3)
Parentheses around the argument x are optional but highly recommended. If you choose not to include parentheses, separate x from the function with a blank space. Example: The following two statements have the same meaning:
LOG(FORECAST)
LOG FORECAST
To find this same information, simply search on the Index of the help files and type in "Square Root".
Keywords: None
References: None |
Problem Statement: After running the business model that runs the CPLEX optimizer on different computers - some machines could not get a value. | Solution: The business model is not triggering the CPLEX error message to show or indicate a licensing problems has occurred. However, if you run GEN then OPT at the MIMI command line, it will show the CPLEX licensing error message at the bottom of the MIMI screen. The workaround is to relicense CPLEX optimizer.
For Windows NT or Windows 2000, do the following steps:
Open a session under the MS-DOS shell.
Change directory to your MIMIHOME value, in this case, MIMIHOME = c:\mimi\bin and type the following:
instlcpx 5D-39-85-B3-B7-FC-A6-58-8D-03-5D-1D-95-86 c:\mimi\
Run the model or optimizer again.
Keywords: None
References: None |
Problem Statement: Is it possible to print the Inventory Grid in Aspen SCM? | Solution: Unfortunately, not. The ability to print the Inventory Grid has never existed in Aspen SCM.
Keywords: None
References: None |
Problem Statement: How to create or edit a Tree Control for use in MIMI workspaces? | Solution: The following are the general steps required to create a Tree Control for use in MIMI workspaces:
Create a Tree Control Set.
The Tree Control Set uses the following CODE keywords: Depth, Label, Action and Expand.
Create a Tree Control Table, using the Tree Control Set as column set.
The Tree Control Table is a character table which defines all nodes of the tree, with each row in the table representing one node of the tree.
Create a dialog set containing only the Window and Tree Controls, specifying the required and optional properties.
To ensure the Tree Control scroll bars remain visible, set the width to be smaller than the Window Control, which in turn should be the same size or smaller than the Workspace frame.
Specify the name of the table (created in step 2) as the DATA property for the Tree Control.
Further details of the specific keywords, parameters and options for Tree Controls can be in the MIMI online Help System.
KeyWords
MIMI workspace
tree control
Keywords: None
References: None |
Problem Statement: Is the MIMI Application Server multiprocessor aware? | Solution: The MIMI application server does not recognize systems with multi processors.
KeyWords:
Keywords: None
References: None |
Problem Statement: MIMI menu sub-list box options do not cascade down or are no longer showing. | Solution: From the MIMI toolbar, go to Options | System.
The System Option dialog will open.
Make sure the "User-Configurable Menus are Cascading" box is checked.
Test the menu again.
Keywords: None
References: None |
Problem Statement: When running the GEN command, MIMI creates image tables for multidimensional or compact incidence tables with the table name preceded by the dollar sign ($). MIMI also creates image tables for the colset of multidimensional/compact incidence tables. Since the maximum length of MIMI set/table names is 8, if the name length of a multidimensional/compact incidence table is 8 and if the first seven characters in the colset name are the same as in the table name, image tables created for the table and for the colset will be the same. In this situation, GEN does not check for duplicate names when creating image tables.
When there are duplicates, MIMI will overwrite these image tables depending on where and the order of the duplicate occurs. As a result, certain COLs/ROWs may not be created. Most possibily, the generated matrix is wrong, and sometimes, it is hard to know the matrix is wrong unless users paid closer attention to the generated matrix because no error is sent out during GEN. | Solution: There are several different ways to avoid the scenario above:
Limit multidimensional/compact incidence table name length to 7 characters
Limit colset of multidimensional/compact incident table name length to 7 characters
For existing models, use "L CHECK"
Currently, L CHECK only checks name lengths of incidence tables used in COLS and ROWS tables.
Incidence tables not called directly in COLS and ROWS are not checked, therefore, manual checking on these name lengths is needed.
It should be noted that a future enhancement to have GEN detect duplicate incidence tables has been identified and will be prioritized for future releases.
KeyWords
GEN
ROW
COL
Keywords: None
References: None |
Problem Statement: INFOMSG ignores the 10th arguement. | Solution: The maximum number of arguments/parameters that any MIMI command supports is 9. INFOMSG appears to be one of these. An argument or parameter is any text or variable separated by a blank space that follows the MIMI command. In this case the :ALLNUM variable is the 10th argument so it is ignored. The message can be separated into two lines or a common practice is to attach text with an underscore, NUMBER_OF_NON-ZERO can be one argument instead of 3.
For example, INFOMSG NUMBER OF NON-ZEROS IN BLEND IS :NONZ OF :ALLNUM will not work. Instead, INFOMSG NUMBER_OF_NON-ZEROS IN BLEND IS :NONZ OF :ALLNUM will work.
KeyWords:
Keywords: None
References: None |
Problem Statement: This can be caused by one or more of several possible problems. See below for a troubleshooting checklist | Solution: The brokers must be running on both the server and the client. The user will need the rights to start the broker as a service.
The user must be able to access the MIMI server. You can check to see if the client is able to see the server by pinging the server.
The user must have logon access to the MIMI server. This is because the MIMI server will ask for the user's network login name and password.
If you are not using DNS on your network, the user will have to type in the TCP/IP address in lieu of the MIMI server's name. If you are using DNS and the server's name is not being recognised, there may be a problem in the name to IP address resolution.
KeyWords
Keywords: None
References: None |
Problem Statement: In Active X Controls, can I loop through a grid by characters (in each row and column) rather than by columns (in each row)? | Solution: You cannot loop through each character. You can only loop through each cell.
Keywords: None
References: None |
Problem Statement: MIMI and Aspen Licence Manager Product Matrix | Solution: Product Version
Aspen Licence Manager
MIMI 4.4 (eSupply Chain Suite CD version 2.0)
ALM Version 2.0
MIMI 5.0 (eSupply Chain Suite CD version 2.1)
ALM Version 2.1, 2.2
MIMI 5.1 (eSupply Chain Suite CD version 2.2)
ALM Version 2.1, 2.2
MIMI 6.0
ALM Version 3.0
Keywords: None
References: None |
Problem Statement: How can a user change the installation drive/directory for MIMI | Solution: When installing MIMI for the first time, you have the option to change the installation drive/directory. During the installation, select the SELECT SUBCOMPONENTS button (from the SELECT PRODUCTS window), select the CHANGE FOLDER button and then MODIFY button.
If MIMI has been previously installed, the MODIFY button will not be available anymore and will be grayed out. During the installation, MIMI sets ASPENMIMIDIRdir entry in the registry which restricts the selection of the MIMI destination folder on future installations. This is because the installation is designed to only have one MIMI installation per machine.
Uninstalling the MIMI application should remove the above mentioned entry from the Registry Settings, thereby allowing the user to choose the drive/directory location for the install of the new MIMI application. If for some reason, the MIMI Uninstall feature does NOT remove ASPENMIMIDIRdir from the Registry Settings the user needs to uninstall the MIMI application and then manually remove the ASPENMIMIDIRdir entry located in KEY_LOCAL_MACHINE\SOFTWARE\AspenTech\Setup. You will then be able to install the new MIMI application on the drive/directory location of your choice.
This will be fixed in the next major MIMI release 7.1 (Targeted for May 2003).
KeyWords
Keywords: None
References: None |
Problem Statement: Macro $LCHK$ is not working properly | Solution: Include the $LCHK$ in $LOAD$ so it runs after the case is loaded.
It is not working because $LCHK$ is executed before the case is loaded. Therefore, if it does not find a case, then whatever is the command inside the $LCHK$ does not get executed. For example, nulling a temp set as it loads the case.
Keywords: None
References: None |
Problem Statement: The RDF parameter (CMAN table entry) is not documented in MIMI Online Help. | Solution: RDF stands for Routing Depath Factor and is a CMAN table code entry. Its default value is 300, the length of working array of backward and forward explosion.
MIMI will sometimes have to generate the Bill Of Materials for a certain product. This is necessary for the BOM command, M MAKE and MRP. This Bill of Materials is stored in a temporary data structure with a default limit of 300 elements. If a product has many components each of which has many components, that limit might be exceeded.
If that is the case, the RDF CMAN entry has to be used in order to enter a new larger structure.
Keywords: None
References: None |
Problem Statement: MIMI Chesapeake Distributed Broker is not running. How can I debug this problem? | Solution: Open up a DOS prompt.
Type brk_serv -console
This command will debug the Distributed MIMI Broker and indicate any problems that are preventing the broker from running.
Keywords: None
References: None |
Problem Statement: Is it possible to perform an SQL JOIN on a table in a database and a table in MIMI? | Solution: The answer is NO because a MIMI table has a different meaning than that of a database table. Therefore, it would not make sense to do a join on a database table and a MIMI table.
KeyWords
SQL
SEQUELINK
Keywords: None
References: None |
Problem Statement: Assignments &1 = ?SET (using a ? variable) and &1 = &2 (using & variable &2) behave differently. | Solution: The rule variables (name starts with ?) and database variables (name starts with $ or &) are different classes of variables, and behave somewhat differently in various situations in the expert system, and only the database variables are usable at the command line.
You can see the different behavior of & (or $) variables vs. ? variables in the two simple rules below:
RTE1
IF AMPSET &1 = "TMPSET1"
AND ?SET = "TMPSET2"
AND &1 = ?SET
THEN RTE1
RTE2
IF AMPSET &1 = "TMPSET1"
AND  AMPSET &2 = "TMPSET2"
AND &1 = &2
THEN RTE2
The line &1 = ?SET in rule RTE1 involves a rule variable (?SET), so that it behaves like AMPSET &1 = ?SET (you cannot execute the same from the command line). The assignment that you execute here, as you can see from the etrace, is the assignment of string TMPSET2 to &variable &1; after that assignment &1 has value "TMPSET2". You execute no set assignment here, and rule RTE1 does not change at all the set TMPSET1.
The line &1 = &2 in rule RTE2 (you can execute the same command also from the command line) performs a text substitution. After the text substitution it becomes TMPSET1 = TMPSET2 (assignment of two sets) and it is like you executed a command from the command line.
KeyWords
RULES
ASSIGNMENT
VARIABLES
Keywords: None
References: None |
Problem Statement: MIMI broker does not work after changing the machine name.
Some symptoms can be:
You cannot create a PROCNAME from the MIMI command line.
You cannot start the Chesapeake broker from the Control Panel | Services. | Solution: MIMI regset.exe needs to be updated when your machine name has changed.
Goto Start | Programs | Administrative tools | Windows NT Diagnostics and find the new machine name.
Goto MIMI\bin\regset.exe and make sure the MIMI Name Server matches the new machine name.
As always, make sure that the broker is running. To check this, click on Start | Control Panel Services and look for Chesapeake broker. The status should be equal to "Started". If not, highlight the Chesapeake broker and click on the "Startup" button.
KeyWords:
Keywords: None
References: None |
Problem Statement: The S ZOOM command zooms IN and OUT on the Planning Board. S ZOOM has two syntaxes:
Zooms IN or OUT by a standard factor defined in CNTLS table. e.g., S ZOOM IN or S ZOOM OUT.
Displays the specified range of time slices (SLI). e.g. S ZOOM start_sli end_sli, here
start_sli: Starting SLI of the range you want to display.
end_sli: Ending SLI of the range you want to display.
When the end_sli is bigger than 787, MIMI will hang. | Solution: There are a couple of options to prevent MIMI from hanging:
Make sure the end_sli is less than 787. (In the current CAPs, end_sli is limited to 600.)
OR...
Change the DTU's in Simulation Time Slice in the CMAN table to a larger number, e.g., change DTU from 1 to 2.
When making this change, the inventory profile will be based on every two hours instead of every one hour if changing DTU from 1 hour to 2 hours.
KeyWords
Planning Board
S ZOOM
SLI
Keywords: None
References: None |
Problem Statement: How to make the POSTFORM command work with MIMI? | Solution: Given that B2B with Aspen Fusion are installed.
Create a text file - e.g. login.txt with two lines:
Username
Password
Then add the following to the end of the postform command
< login.txt
Note: Make sure pathnames are in the right directory to run and find things. Also, the space in "program files" directory will not make postform work properly. Therefore:
Create a simple directory name (I used c:\test).
Move all the postform EXEs and DLLs in there.
Move the test.bat and login.txt files in there as well.
In test.bat, before calling the postform command, enter the following two commands:
C:
cd \test
From MIMI, type "SYS c:\test\test.bat" without the quotes, and hit the "Run" button
Keywords: None
References: None |
Problem Statement: How to install CPLEX licensing under the UNIX environment. | Solution: In addition to installing the new license number received from AspenTech, user will have to check if the MIMIHOME environment variable is correctly set up. This is a step-by-step-procedure that the user can follow in order to install correctly CPLEX licensing under UNIX environment.
Obtain a new license number from Aspen Tech (this is required for error 32104 LICENSE CODE HAS EXPIRED).
Edit the install.cplex.* file with the new license number (use VI or another editing tool). The file to be edited is located in the /MIMI/bin directory.
Perform a shutdown and restart the system.
Logon as mimiadm.
Type echo $MIMIHOME. If nothing displays, type export MIMIHOME=/mimi500 (mimi500 is an example of MIMI directory name). Type echo $MIMIHOME again to check.
Verify that mimiadm is the owner of the files in /mimi500 by typing ls -al /mimi500. Example:
total 86
drwxrwxrwx 7 root sys 1024 Mar 27 08:39 .
drwxr-xr-x 26 root root 4096 Mar 29 22:05 ..
rwxr-xr-x 1 mimiadm users 8145 Jan 14 2000 .mwmrc
rwxr-xr-x 1 mimiadm users 17799 Mar 27 13:13 .profile
rwxr-xr-x 1 mimiadm users 2828 Jan 14 2000 .xinitrc
drwxrwxrwx 3 mimiadm users 1024 Mar 29 08:34 bin
drwxrwxrwx 2 mimiadm users 1024 Mar 27 08:13 cases
drwxrwxrwx 2 mimiadm users 1024 Mar 27 08:13 images
rw-rw-r-- 1 mimiadm users 2381 Aug 7 2000 install.lst
drwxrwxrwx 4 mimiadm users 2048 Mar 27 08:27 lib
drwxr-xr-x 2 mimiadm users 1024 Mar 27 08:51 license
Verify that cpxlicense file has execute permission by typing cd /mimi500/bin then cd ll cpxlicense. Example: rwxr-xr-x 1 mimiadm users 45216 Feb 2 2000 cpxlicense
Verify that LP OPT is in the last line of tape.inf file by typing cd /mimi500/lib then ll tape* Example: rw-r----- 1 mimiadm users 170 Aug 7 2000 tape.inf Then type cat tape.inf | more Example: PB E M J LP OPT (This is the last line of the file).
Type echo $SHELL. If not /bin/ksh, type ksh.
Type PATH=/mimi500/bin:$PATH ; export PATH
Execute the appropriate install file by typing install.cplex.only
Test CPLEX by loading any MIMI Linear Programming model.
Additional information can be obtained in the Licensing the CPLEX Optimizer chapter of the CPLEX Manual.
Keywords: None
References: None |
Problem Statement: How to print external bitmaps or jpeg files from Aspen SCM. | Solution: Typing the following statement from the command line will print the bitmap (or jpeg) with no other user intervention:
SYS MSPAINT /p c:\mimi\bitmap\ filename.bmp
However, you can also write a rule and input the file and print string so that it prints automatically by adding the following lines to your rule.
This will set a variable to the file name you want to print:
AND :F = 'filename.jpg'
This will set a variable to the file path where the bitmap or jpeg is located:
AND :D = "c:\mimi\bitmap\"
This will set a variable to join the 2 preceding variables in order to create a full path of the file location:
AND :SC = ':D:F'
Then, add the following line to your rule in order to have the file printed:
AND SYS MSPAINT /p :SC
IMPORTANT NOTES:
If you take out the /p it stops and waits for your commands in MSPaint then exit back to Aspen SCM.
If the file is too big (too wide or too tall), it prints that file to be the exact size of the 8.5 x 11 paper in the printer.
KeyWords
JPEG
TIFF
graphics
graphs
printing
Keywords: None
References: None |
Problem Statement: What are the minimum memory requirements to run MIMI. | Solution: The minimum memory requirements to run MIMI is 256 MB of RAM. Add roughly 5 meg per user plus the MIMI model size. Example: If you have six users each with a 50 meg model, you should have 336+ megabytes of physical RAM.
Keywords: None
References: None |
Problem Statement: How to create a list of infeasibilities in the ERROR window table using CPLEX optimizer and ALGO parameter set to DUAL ? | Solution: Recently, a customer using parameter ALGO set to DUAL in the CCPLEX table, obtained an infeasibility error, but NO infeasible cols or rows in INFO table, so there was no list of infeasibilities. (He also tried with the pre-solve indicator set to YES and NO and obtained the same result).
After running command OPT, a message that comes back says "LP is PRESOLVE INFEASIBLE or UNBOUNDED". In order to get a list of infeasibilities, the two following actions have to be performed:
Changing ALGO to PRIMAL in CCPLEX. If the problem is unbounded using DUAL, then it is infeasible using PRIMAL (and vice versa) and the ERROR window will come up with a list of infeasibilities, which does correspond to the unbounded vectors in the DUAL.
If the same message still occurs, then the pre-solve indicator has to be turned off. This is done by setting PREIND to NO in CCPLEX. Running OPT again should now result in showing the list of infeasibilities. The pre-solve indicator has to be turned back on when all is fixed.
Notice that the above is not applicable to XPRESS optimizer.
Keywords: None
References: None |
Problem Statement: When I open up a set, the notes and part of the code is being truncated. | Solution: Start MIMI and open the case in which you are having this problem
Go to Options on the tool bar
Go to System
Click on the Editors tab
At the font area (in the lower right of the window) click on the drop down box
Select header
Click on the browse box (the box with ... in it)
Select Courier for the font. Select Font Style as regular. Select size as 9
This should fix the problem.
KeyWords:
Keywords: None
References: None |
Problem Statement: Efficient Matrix Generation Guidelines. | Solution: Efficient matrix generation requires careful design of the MIMI LP definition tables (COEF, POLI, COLS, ROWS and referenced incidence and data tables) One of the most important areas in this is the careful use of Compact Incidence tables (some people think of these as MIMI Multi-Dimensional tables). As a first step in focussing on the area in which there may be some generation issues - it is useful to determine the generation time for each generic column. The generation time for each column can be seen by making sure the MIMI Message Log (under the Window menu) is turned on when the matrix is being generated.
Some Guidelines
Maximize using the generic column incidence tables. Define as many sets as possible in the column domain. Avoid using compact incidence tables in the row domain (ROWS) because each column generated will require looping over the entire row compact incidence table row set. It is better to set the required row domain set indicies in the column domain where possible.
Avoid using implied incidence (sparse data tables referenced by COEF). Whenever there are sparse data tables in - for example YIELDS, always use incidence tables to avoid the generator setting up to build a variable only to find that the referenced matrix coefficient (in COEF) is zero.
If using hierarchical incidence structures (where one incidence table points to another) - try to keep the most sparse incidence structures at the highest level. Often it makes sense to have a compact incidence table at the top level of the hierarchy (referenced in COLS) point to other tables. If this is the case the compact incidence tables should have all the domain sets used by tables further down in the hierarchy where possible. Never have another compact incidence table in the structure which has a rowset which is not part of the column domain.
Coefficient tables and matrix rim (bounds and right hand side tables) should be associated with incidence tables. A good structure for these tables is to use the same rowset as the compact incidence table for these data tables. This avoids the need to do any searching or looping as the required data can be obtained by a direct look up based on the current index of the domain sets.
Keywords: None
References: None |
Problem Statement: How can I tell if my machine has Distributed MIMI or Classic MIMI installed on it? | Solution: Go into MIMI and click on File --> Open and look at the open cases dialog. If the dialog has 4 boxes (1)Filenames, (2) Directories, (3) Drives and (4)Database Server List that means your machine is running Distributed MIMI. In Classic MIMI, the Database Server List does not appear.
KeyWords:
Keywords: None
References: None |
Problem Statement: How to move a case from a UNIX operating system to a Windows environment. | Solution: 1. UNIX box: Run the cas2dat utility on the case to create a *.data file, i.e. - MODEL.data.
2. UNIX box: FTP the MODEL.data file to the windows box. Be sure to transfer the file in ASCII mode.
3. WINDOWS box: Rename the MODEL.data file to MODEL.dat.
4. WINDOWS box: Run the dat2cas utility (Start | Programs | AspenTech | Aspen Supply Chain Suite | Aspen SCM Utilities --> DAT2CAS Conversion). Be sure to name the new file with a *.cas extension, i.e. - MODEL.cas.
Load the new case file using the Windows installation!
Keywords: CAS2DAT
DAT2CAS
UNIX
AIX
DIGITAL UNIX
HP-UX
SOLARIS
References: None |
Problem Statement: How do you get rid of the hour-glass cursor on the Aspentech (or any other) bitmap screen in the workspace when you first load your MIMI model? | Solution: Anyone using the workspace with a bitmap in the initial display screen part of the workspace may know the problem, whereby when you first open up your model, the cursor stays as an hour-glass symbol while it is on this part of the screen, even though the load has finished. Also, if you move the cursor slowly onto this part of the screen from the menu tree part, it can stay as the move pane symbol (something like <-||->).
A simple workaround to get the cursor to go back to the normal arrow when you load the case and when you move onto this part of the screen is to make the screen into a giant button, because when the cursor hovers over a button it knows that the screen is active and sets the cursor to the normal style.
In the following example, a BIGBUTTON widget was added to the bitmap dialog:
WINDOW WINDOW
VERSION 2
GEOMETRY
850X650+0+0
BIGBUTTON
PUSHBUTTON
GEOMETRY
815X600+0+0
STYLE
HIDDEN
IMAGE
IMAGE
PIXMAP_SPLASH
PROCESS3.BMP
GEOMETRY
815X600+0+0
KeyWords
MIMI workspace
bitmap graphics
cursor
Keywords: None
References: None |
Problem Statement: Slow data transfer when writing data from MIMI to an external database via SequeLink | Solution: Writing out a moderately large MIMI character table to an external database takes longer than expected. For example, the exporting time of an 840 row by 10 column table takes approximate 600 seconds.
To reduce this time, make sure that all SQL outputs reference String tables. In our example, this reduced the exporting time to 13 seconds.
KeyWords
Keywords: None
References: None |
Problem Statement: The listbox is failing to display the tab settings in a dialog. | Solution: The listbox fails to display the tab settings when the dialog is not getting run by the Version 2 dialog engine. Even though the "Version 2" string is specified in the top-level window definition, the presence of TOP, LEFT, etc. forces the dialog to be run using the old dialog run-time engine instead.
You can tell if a dialog is Version 2 compliant by bringing it up in the Dialog Builder. If MIMI complains that there are things there that need a conversion, you have a Version 1 dialog.
Note: The on-line help will include a statement that these attachment keywords are not "Version 2" compliant and that, if used, it will cause the dialog to be run with the old dialog run-time engine. This is important since STYLEs are only supported by the Version 2 engine.
KeyWords
STYLE TABSET in the List Box
Keywords: None
References: None |
Problem Statement: Why you can't change the color of the text displayed inside the Planning Board pucks when using BCODEs. | Solution: The BCODE color can not be changed because it uses the same color as Window Background which is specified in SYSCOL table.
Keywords: BCODE
References: None |
Problem Statement: The CA Remote Procedure Call Server service of BrightStor ARCserve Backup (a Computer Associates product) prevents the NobelNet Portmapper service from starting.
Since the Chesapeake Broker service is dependant of the NobleNet Portmapper service, it will also not start and Aspen SCM will fail to load.
The CA Remote Procedure Call Server service is using the same port (111) as the NobleNet Portmapper which creates a conflict. | Solution: To avoid this problem, follow the instructions below.
Step 1 - Change the CA Remote Procedure call server service status
Open the Control Panel.
Select the Administrative Tools, then Services.
Right click on the service and change the AUTOMATIC status to MANUAL.
Reboot the machine.
After rebooting the machine, the CA Remote Procedure Call Server service will not start anymore and the NobelNet Portmapper service will start as expected.
Notice that if you have installed BrightStor ARCserve Backup in a Microsoft Cluster Services environment, you can change the AUTOMATIC status of the CA Remote Procedure call server service to DISABLED.
This enables you to avoid similar port conflicts after the system has completed the boot process.
Step 2 - Prevent the BrightStor ARCserve Backup services to initialize before the NobleNet Portmapper service
BrightStor ARCserve Backup can work with external Portmappers (SFU 3.0, Noblenet Portmapper, StorageTek Libattach etc.).
However, during the machine boot up sequence, BrightStor ARCserve Backup services may try to initialize before the external portmapper has fully initialized.
Under these circumstances, BrightStor ARCserve Backup services then fail to initialize.
To avoid this problem, perform the following steps:
Create the following registry key: HKEY_LOCAL_MACHINE\Software\ComputerAssociates\BrightStor ARCserve Backup\Base\Portmap
Create the DWORD DelayedRegistration under this key.
Assign a decimal value for this key, indicating the number of minutes BrightStor ARCserve Backup services wait before initializing portmapper registration. For example, DelayedRegistration=2 causes all BrightStor ARCserve Backup services to start but not register with the portmapper for 2 minutes after startup.
KeyWords
BRIGHTSTOR
PORTMAPPER
COMPUTER ASSOCIATES
NOBLENET
CHESAPEAKE
BROKER
Keywords: None
References: None |
Problem Statement: Can ALM (AspenTech License Manager) be used if a user wants to work off of the network? | Solution: ALM keys (by default) are set up to be tied to the Ethernet address. This will not work successfully if the user is disconnected from the network.
To get around this problem, you need to tie the key to the disk serial number of the hard drive, instead of the Ethernet address.
Click on Start --> Programs --> AspenTech --> Aspen License Manager --> Aspen Host ID Information Tool.
Copy the Disk Serial Number, by highlighting it and type Ctrl-C to copy the text.
Go to http://support.aspentech.com and follow the licensing steps as before.
When prompted for the License Server information, click on the "Alternative Network Server" radio button. Then, in the field next to it, type Ctrl-P to paste in the Disk Serial number.
Exchange the existing license on your PC, with the new license which is now tied to your Disk Serial Number.
Click on Start - Programs --> AspenTech --> Aspen License Manager --> Aspen License Manager Admin Tool.
Choose "Configure Using Services" if it is not already chosen.
Click on the "Start/Stop/Reread" tab and click on "ReRead License File".
Try running MIMI again while disconnected from the network.
Please contact the MIMI help desk at 888-996-7100, option 3, option 1 if you experience any problems.
KeyWords:
Keywords: None
References: None |
Problem Statement: How can I quickly find the ETHERNET ADDR, DISK SERIAL NUM, HOSTNAME? | Solution: For licensing purposes, you need the ETHERNET ADDR, DISK SERIAL NUM, HOSTNAME of the PC where MIMI will be installed. This information is provided by the Aspen License Manager 3.0 utility "Aspen Host ID Information Tool".
This tech tip tells you how you can retrieve the same information in a quick and easy way in case you don't have that utility installed. First get to a DOS prompt (click on Start / Run... and type CMD).
DISK SERIAL NUM
Be sure that your current drive is your local hard disk. If not type C: from the DOS prompt. Type DIR from the DOS prompt. You'll find the disk serial number on the 2nd line, indicated as "Volume Serial Number". Just leave out the dash. Example:
Volume Serial Number is 50CC-62D0
HOSTNAME and ETHERNET ADDR
Type IPCONFIG/ALL from the DOS prompt. You'll find the host name in the line "Host Name" and the ethernet address in the line "Physical Address". Just leave out the dashes. Example:
Host Name . . . . . . . . . . . . : myhost2k
Physical Address. . . . . . . . . : 00-D2-B0-7D-5E-DE
KeyWords
Aspen Host ID Information Tool
DISK SERIAL NUM
Disk Serial Number
HOSTNAME
Host Name
ETHERNET ADDR
Ethernet Address
ALM
Aspen License Manager
Keywords: None
References: None |
Problem Statement: Error message about LISA not being properly licensed. | Solution: LISA executable must be run while in the C:\MIMI\BIN directory or it will crash and give the error message about not being properly licensed.
KeyWords:
Keywords: None
References: None |
Problem Statement: Does MIMI attach to a Windows NT Server? | Solution: MIMI will attach to a Windows NT Server only for Distributed MIMI (Light Client). For the Application Client, it does not need to attach to an NT server.
KeyWords:
Keywords: None
References: None |
Problem Statement: The links to external libraries are missing and the rules/macros are blank when opening an Aspen SCM model. | Solution: The cause appears to be a corrupt $TCASES. Running CMPRCASE will likely fix this problem temporarily, but here is a permanent solution:
1. Write down or copy the contents of $CASES and $TCASES to Word or Notepad.
2. Null out $CASES and $TCASES in the original case.
2. Exit out of Aspen SCM.
3. Run cas2dat and dat2cas.
4. Load the new case and repopulate $CASES and $TCASES with the same data as before.
5. Save the case.
6. Reload the case again and the remote cases should load OK this time.
KeyWords
LOAD
OPEN
CORRUPT
ERROR
DEPENDENT
INDEPENDENT
Keywords: None
References: None |
Problem Statement: Unable to import Data into MIMI Using ODBC Drivers 3.x | Solution: The data is not importng into MIMI because of the ODBC drivers. The latest version of ODBC has a larger default capacity; therefore, it can handle larger data coming from a database and the data will not be truncated.
If you see the following error from the SQLMSG file, "ORACLE[ODBC]String Data, right truncated." use any of the following recommendations:
First workaround
Install a version of MIMI/SequeLink that is compatible with the database. SequeLink is middleware software that gets shipped on a separate CD-ROM. The latest version of the SequeLink Client and Server is 4.5.1 for MIMI 5.0 and above. This installation will ensure the correct version of ODBC drivers is used with the MIMI installation.
Second workaround
Do not use the SequeLink software and only use the ODBC drivers provided by Microsoft. You can download the latest ODBC drivers from the Microsoft webpage. Make sure that the MIMI macro or connect statement is now pointing to the new version of ODBC. This is not a supported type of interface with MIMI.
Third workaround
Reduce the size of the data length exporting from a database into MIMI.
KeyWords
Keywords: None
References: None |
Problem Statement: This tech tip describes the hardware and software requirements for running Aspen SCM. | Solution: PLATFORM
Windows 2000 Server, Windows 2003 Server, Windows 2000 Professional, Windows XP Professional
PROCESSOR
Minimum: Pentium (X86) 1 GHz
Notes:
- "Pentium(X86)" is not meant to indicate that only Intel processors are recommended, as others are also OK.
- There are other faster processors that are available today, so this specification is given as a minimum.
MEMORY
Minimum: 512 MB RAM
Notes:
- Memory is truly dependent upon the size of the Aspen SCM model. For example, the indicated memory amount may not be sufficient for a good sized planning application.
HARD DISK
Minimum: 500 MB free space
Recommended: 2 GB free space
ADDITIONAL HW SPECIFICATIONS
Color graphics display should support at least 256 colors
Applications that employ the Planning Board should have at least a 17" monitor or larger
Video card should have at least 4MB RAM
CD-ROM reader for Aspen SCM versions 8.0 and below
DVD reader for Aspen SCM versions 2004.0 and above
Notes:
- Starting from October 1, 2006 Unix is no longer supported.
- Inside Knowledge Base solution 116944 you can see the Aspen SCM versions supported until October 1, 2006 for each Unix platform and operating system.
- Windows XP Home will not work.
- Windows XP is supported only for Aspen SCM versions 7.0 and above.
Keywords: ENVIRONMENT
PLATFORM
OPERATING SYSTEM
OS
HW
SW
MIMI
HARDWARE
SOFTWARE
CPU
HD
References: None |
Problem Statement: Preventing users from opening the same MIMI model at the same time via the MIMI Request Broker. | Solution: The Chesapeake Distributed MIMI Request Broker - often called MIMI Broker, or Request Broker or simply Broker - is a Windows service that manages communications between MIMI models. It performs three functions:
1. Request handling - Receiving incoming requests and directing them to the appropriate process
2. Server startup - Starting up database, application, and Interface Server MIMI modules as necessary
3. Name service - Communicating the names of the different processes to each other
During the installation of MIMI you are asked the name of the MIMI Server.
An example implementation that uses the Request Broker and the MIMI Server.
? You have MIMI installed on two PC's (e.g. SRV1 and SRV2) and you want to prevent two different users on those servers from opening the same case at the same time. A message will be displayed when someone tries to do that.
? This can be obtained by putting a PROCNAME command in the $LOAD$ macro of the case. See below how the load macro could be.
When case is loading, if another MIMI case with the same "process name" is running, then the command PROCNAME will give an error and the user will get an error message as described in the last 5 lines of the $LOAD$ macro.
Explanation of line AMPSET &RETURN = SCPARM(PROCNAME,1)
In this example, table SCPARM, at row PROCNAME, column 1, allows you to define a process name different from the case name. This is not necessary in general.
? What can prevent this system from working?
1. The MIMI Broker must be started on both servers, otherwise PROCNAME will not work
2. You cannot have different Name Server names defined in the registry of the same computer. This will also prevent the MIMI processes (e.g the MIMI models on SRV1 and SRV2) to communicate with each other. To check this, you check the value of the MIMI_NAME_SERVER key in the registry on the different machines to see if they are the same.
Example:
on the SRV1:
HKLM\Software\Aspentech\AspenMIMI\6.2\MIMI_NAME_SERVER "COSMOS"
on the SRV2:
HKLM\Software\Aspentech\AspenMIMI\8.0\MIMI_NAME_SERVER "NAMESERVER2"
3. A diagnostics utility for the Broker is available. You can run it on each server where MIMI is installed. The executable is brk_diagnostic.exe and is located in the \Program Files\AspenTech\AspenMIMI\Bin directory. The picture below shows an example report provided by this utility.
4. Note that the versions of the Broker on all machines MUST be the same if you want those MIMI models to talk to each other.
KeyWords
CHESAPEAKE DISTRIBUTED MIMI REQUEST BROKER
MIMI NAME SERVER
PROCNAME
Keywords: None
References: None |
Problem Statement: Dashes (and other characters) in the first line of a rule set cause COLLECT and LINK to fail. | Solution: See the example below. If the first line of a rule set (like below) contains dashes (or other characters), this will cause the rule set not to be recognized as such. Therefore, COLLECT will fail to populate RULES, and as a consequence of this, LINK will also fail. In turn, executing the rule will result in an UNKNOWN error message.
Code Description
--------- This is my rule
RULENAME
IF TABLE1 = NULL
AND ?BIN IN BIN
To get around this, simply remove the dashes (or other characters) from the Code portion of the first line of the rule set.
Code Description
RULENAME
IF TABLE1 = NULL
AND ?BIN IN BIN
You should remember that, unless you add a new rule set to the case, or change the name of an existing rule set, there is no need to run COLLECT, and even then it is probably better to just manually edit RULES to insert the names of the new rule sets.
Note that LINK links all the rules in all the rule sets listed in RULES (also can be a different set as specified in CNTLE, but that feature is rarely used).
Keywords: RULE
RULES
RULESET
$RULE
$PRED
PREDICATE
References: None |
Problem Statement: Is it possible to print the Planning Board to a file? | Solution: Yes, this is possible with the SCM command WINSHOT . The WINSHOT command sends the Planning Board to a file (see picture below), which can then be printed.
You can execute this command from the SCM command line (press F3):
WINSHOT window_name output_file
window_name :
You can see the window name enclosed in brackets in the title bar on the top of the window.
For the planning board it is MAIN1, MAIN2, etc.
output_file :
Output file name. These formats (and extensions) are supported: bitmap (.bmp), JPEG (.jpg) and Portable Network Graphics (.png).
It is generated in the folder where the case file is (if no path is indicated), otherwise in the specified path.
For example:
WINSHOT MAIN1 PLANBOARD.JPG
where MAIN1 is the name of a Planning Board window and PLANBOARD.JPG is the output file name
For further details, you can look for the WINSHOT command in the on-line help.
KeyWords
PLANNING BOARD
PB
WINSHOT
PRINTING
Keywords: None
References: None |
Problem Statement: Can I use MimiX (Active-X) with MS Office 95 or an earlier version of Excel? | Solution: No. Any MS-Office product, earlier than MS Office 97 does not support Active X.
KeyWords
Keywords: None
References: None |
Problem Statement: How do you print out the contents of the Problems Window in Aspen SCM? | Solution: If a user wants to print out the contents of the Problems Window (OPTIONS / PROBLEMS when the Planning Board is opened), he needs to use the command S PROBLEM (shortcut is S PROB) from the command line. This command writes the contents of the Problem Window to the INFO table.
The table INFO can then be printed as report.
The arguments PRO, TIME and COST can be used to sort the report (S PROB[LEM] [PRO | TIME | COST]).
In order to clean up INFO table after this operation is completed, use the command INFOMSG RESET from the command line.
KeyWords:
S PROB
S PROBLEM
Keywords: None
References: None |
Problem Statement: How can I quickly find the ETHERNET ADDR, DISK SERIAL NUM, HOSTNAME? | Solution: For licensing purposes, you need the ETHERNET ADDR, DISK SERIAL NUM, HOSTNAME of the PC where MIMI will be installed. This information is provided by the Aspen License Manager 3.0 utility "Aspen Host ID Information Tool".
This tech tip tells you how you can retrieve the same information in a quick and easy way in case you don't have that utility installed. First get to a DOS prompt (click on Start / Run... and type CMD).
DISK SERIAL NUM
Be sure that your current drive is your local hard disk. If not type C: from the DOS prompt. Type DIR from the DOS prompt. You'll find the disk serial number on the 2nd line, indicated as "Volume Serial Number". Just leave out the dash. Example:
Volume Serial Number is 50CC-62D0
HOSTNAME and ETHERNET ADDR
Type IPCONFIG/ALL from the DOS prompt. You'll find the host name in the line "Host Name" and the ethernet address in the line "Physical Address". Just leave out the dashes. Example:
Host Name . . . . . . . . . . . . : myhost2k
Physical Address. . . . . . . . . : 00-D2-B0-7D-5E-DE
KeyWords
Aspen Host ID Information Tool
DISK SERIAL NUM
Disk Serial Number
HOSTNAME
Host Name
ETHERNET ADDR
Ethernet Address
ALM
Aspen License Manager
Keywords: None
References: None |
Problem Statement: If an actitivity is moved in the schedule, does it automatically trigger a rule in TDAT? | Solution: The before/after macros in the Planning Board were added to MIMI in version 6.2. You can look up $PBBEF and $PBAFT in the user manual to learn how to use this feature.
Go to the Documentation on the Techncial Support site.
Select the Aspen MIMI product and then the Aspen MIMI Scheduling 7.0 User Guide. Go to the Planning Board section and select "Running Before and After Procedures When you Manipulate Activities."
KeyWords
Planning Board
$PBBEF
$PBAFT
Keywords: None
References: None |
Problem Statement: DMFCST OPTIMAL does not generate a forecast for some members. | Solution: DMFCST OPTIMAL does not generate a forecast for some members.
The OPTIMAL keyword in the code of the forecast method set invokes the forecasting method automatically. However, it is difficult to justify using the OPTIMAL method when there is little history. here are some recommendations for an easy way to use a default forecast method for those entries that have little history:
Pick a method which needs very little history to produce a forecast, e.g. ONE_EXP_SMOOTH or PERIOD_AVERAGE.
Forecast everything by that method and save it to a temporary table.
Forecast everything by the OPTIMAL method.
Loop over RDMWORK and find entries that have no forecast method and replace them with the default forecast.
KeyWords
Keywords: None
References: None |
Problem Statement: Does MIMI install as a Windows NT Service ? | Solution: Yes, the MIMI Broker installs itself as a service.
Keywords: None
References: None |
Problem Statement: I am using Citrix Terminal Server and when a user runs MIMI, the server CPU maxes out and other users are unable to run their applications. | Solution: Usually, a Citrix administrator will setup the server and allocate server resources to the profile of each user that logs into the Citrix server. In this case, one of two things may have happened: 1) The server has not been setup in this manner and the users do not have specified resource profiles, or 2) The server has maxed out its physical resources (this will happen usually with physical RAM). The solution is to correctly setup the resource profiles or to reduce the MIMI task priority.
KeyWords:
Keywords: None
References: None |
Problem Statement: Error message M0969 when opening a case file | Solution: Under certain circumstances, the follwing error message can occur while attempting to open a CAPS case file:
"M0969: Error opening cas file, check file permissions"
This message appears in the message bar at the bottom of MIMI application (FIG 1).
FIG 1
One of the reasons for this message to occur is when table $TCASES (defines the fully qualified file name of each remote case) does not point to the correct paths or remote cases of the Shared Libraries (FIG 2).
FIG 2
In order to resolve this problem, load your CAPS case file, open any set or tables and open the Attributes window.
In the Load Case parameter, verify that the remote Shared Libaries cases in the list box match the cases indicated in $TCASES table (FIG 3).
Also verify that $TCASES table is pointing to the correct Shared Libraries cases location.
FIG 3
KeyWords
$TCASES
LOAD CASE
ATTRIBUTES
SHARED LIBRARIES
CAPS
M0969
Keywords: None
References: None |
Problem Statement: How to properly uninstall MIMI. | Solution: The proper way to uninstall MIMI is by going to Start --> Programs --> MIMI --> Uninstall MIMI. Do not use the Add/Remove utility in the Control Panel. This utility may corrupt the license file.
KeyWords
Keywords: None
References: None |
Problem Statement: I am unable to get the MimiX_ sample2.xls to run. The only way I can get the active x sample.xls to run on the Lite Client, is to have the case open on the Server. The case can not be open on the client side. Is this correct? Is there any way to run active x from Application Client without having to have the case open on the server? | Solution: MimiX cannot connect to Lite Client nor communicate directly with Lite Client. MimiX can only communicate with an Application Client or Application Server. The Application Client that I'm referring to is not the stand-alone MIMI. It is the Application Client that utilizes the Distributed component.
KeyWords:
Keywords: None
References: None |
Problem Statement: How can I change the language of .cas files when the user does not know the original language? For example, how can I change from Japanese to English when users do not know Japanese? | Solution: The following steps can be used to change the language.
1. Click the + on the third item from the bottom in the tree menu.
2. Click the sub-option that is now shown.
3. In the dialog now displayed, the top drop-down option-menu has the list of available languages. Drop it down and choose the one you want. If they are all in Japanese, the first item is US English, the second is UK English.
4. Press the first (left most) push-button at the bottom of the dialog. You should now see everything in your selected language.
Even after doing this, some things might still be in Japanese. That would be customization done for the clients that were not done with the CAP language support. It is much faster to not use the language support for custom items but it does not help later if someone who does not know the language has to work with it.
Keywords: cas language
Change language
Language control
References: None |
Problem Statement: With MIMI versions up to 7.0.x, if you try to bring words such as Ouville-la-Riviere, Koln, Galzau from your flat files into MIMI tables using utility DMREAD or TREAD, you will see bad characters inside MIMI tables and sets instead of the foreign characters. | Solution: If you want to put only a few words containing non-English characters, then you can simply double click the cell of a MIMI table or set from the set/table editor and paste them in: you will correctly see your characters. Do not just click once and simply select the cell and paste, because you would still see the bad characters!
Anyway, most of the time you will have to import big quantities of data on a regular basis into your MIMI sets and tables. What can you do then?
If you have MIMI version 7.0.x and below, you have to be sure that your flat files are in DOS format. Then you can use DMREAD or TREAD to import your data. If the flat files are not in DOS format, you can use the AspenMIMI utility called ASPENTEXT2DOS.EXE which was made available starting from MIMI 6.2. You can find it in the MIMI submenu of the Windows' Start menu called "Aspen MIMI Utilities". This solution does not apply to SREAD.
The issue of displaying non-English characters in MIMI was fixed in version 7.1.
As you can read in the MIMI 7.1 Release Notes about CQ 86195:
? MIMI now uses the ANSI character set.
? This change was made to support display of the European Currency (Euro) symbol.
? Implementing the ANSI character set resulted in the following additional changes in MIMI:
o MIMI now supports the copyright and trademark symbols, and other ANSI characters, such as European language accents.
o The AspenText2Dos utility is now obsolete and should no longer be used.
o The cas2dat and dat2cas utilities have been modified to accept the European Currency (Euro) symbol.
o The BFILL command has been modified to accept the Euro symbol.
KeyWords:
DMREAD
TREAD
SREAD
TEXT2DOS
Foreign characters
ANSI character set
Keywords: None
References: None |
Problem Statement: How can I display or change the screen resolution in an Active Screen? | Solution: You can display and change the screen resolution from the menu tree Options>Settings, but if you are in an active screen and do not want to back out and go to the menu tree you can easily see the screen resolution setting from the Command Line:
F3 - Command Line
Enter AMPSET&1 = SCRNRES(@,C)
Click Run
Enter MSG&1
Click Run
The screen resolution displays on the message bar.
You cannot change the resolution in the active screen; you must go to the menu tree to do that.
Keywords: Screen Resolution
References: None |
Problem Statement: How do you change the Activity Editor font and size in Aspen SCM? | Solution: The activity editor font will use the same font as the planning board label font.
You can change the font by click the Options --> System menu option in Aspen SCM and then click the last tab, Windows Attributes tab. In the Window Attributes tab sheet, there is a button under the Planning Board, called Label Font. If you changed Label Font for the Planning Board, the Activity Editor font will be changed as well.
Keywords: None
References: None |
Problem Statement: How do you change the language in Aspen Supply Chain Management (SCM)? | Solution: Go to the \mimi\bin\ directory. Look for the following *.bat files in this subdirectory:
? Converttoenglish.bat
? Converttofrench.bat
? Converttogerman.bat
? Converttoitalian.bat
? Converttojapanese.bat
? Converttospanish.bat
Exit SCM, and double-click on the appropriate *.bat file. When you restart Aspen Supply Chain Management (SCM), the menus will display in the appropriate language.
IMPORTANT NOTES:
1: Localized operating systems may be necessary for characters to display correctly, especially in Japanese. 2: Help files have not yet been translated for all supported languages.
Keywords: None
References: None |
Problem Statement: MIMI is not responding to external requests or communications. | Solution: MIMI AC is isolated by default; therefore, MIMI will not respond to external requests. MimiX, MIMI Web, and Distributed MIMI all require you to run the ISOLATION OFF command in order to communicate to external requests.
To turn isolation mode off, type ISOLATION OFF on the MIMI AC command line
For MIMI Web to connect to a live Aspen MIMI process, isolation mode must be off (common error).
Recommended: Put ISOLATION OFF into $LOAD$ (this macro gets run when the case is loaded)
KeyWords
Keywords: None
References: None |
Problem Statement: Does Aspen SCM operate on a Blade Server? | Solution: AspenTech did not do official test on blade servers; here the operating system is the key rather than the hardware. Blade Servers should not be an issue however AspenTech cannot certify it unless it is tested.
Keywords: Servers
Platform
Computer
References: None |
Problem Statement: Does the scratch file which is created by CMPRCASE remain if the compression is unsuccessful? | Solution: Yes. A scratch file (has extension SCR - e.g. CMP_1820.scr) will remain on the user's PC if the compression was unsuccessful. CMPRCASE can fail for various reasons. For example, when some problems occur when reading data in during the compression, if the case file is locked, if the system runs out of the space, etc. To understand the cause, it is important to know how CMPRCASE is executed.
CMPRCASE compresses a case in three steps:
1. Reads data from the original case, gets rid of wasted space, then writes data to the SCR file.
2. Writes data back to the original case file.
3. Deletes the scr file.
How can a case be locked?
? If CMPRCASE fails in any of these steps, you will see a scr file remain. If the case is being accessed by another program, the case can be locked by that program. If the case is locked, step 2 will fail.
What could happen if a program automatically copies the case into another folder and tries to open it during case compression, specifically, would this case miss some data?
? If a program copies the case during step 2, the case may miss some data and CMPRCASE would fail.
What would cause both the scratch file and the original case to be the same size?
? If any problem occurs between step 2 and step 3, the scr file and the original case file can have the same size. Also, if there is no wasted space in the original case and CMPRCASE fails to open the case for step 2, the scr file and the original case file can also have the same size.
Keywords: CMPRCASE
case compression
CAS2DAT
DAT2CAS
References: None |
Problem Statement: A user is working with a case where the TDAT(LA) parameter is set and when M NET CHANGE is used to create new activities, the LA (LOOKAHEAD) parameter has clearly not been taken into consideration when activities are created.
Does the TDAT(LA) option work ?
If so, how ? | Solution: Notice that the TDAT(LA) option will have some impact on the case file only if it uses algorithm MRP (it is a version of the MAKE algorithm that handles fast unconstrained MRP).
The LOOKAHEAD policy is used for looking ahead in computing lot sizes.
This policy is turned on by the presence of the LA (LOOKAHEAD) entry in the HTD column in the TDAT table.
It tries to compute a lot size for the next n date time units where n comes from TDAT(@,LA).
The LOOKAHEAD value n can be represented by a constant value or a table. Lot size Policy can be ADJUST or INCRE.
Even though the LA entry exists in the HTD set, an inventory type (TYI) with n blank or zero will ignore the LOOKAHEAD logic.
Furthermore, the LOOKAHEAD number (in unit of time period) is decreased by the current time period index of the activity, so user will have to increase TDAT(LA) to compensate this until the LOOKAHEAD computation routine hits the end of simulation horizon.
Example
User has an activity in time period 5.
TDAT(LA) is set to be something that will be interpreted as 4 time period ahead.
It means that from time period 5, user would like to look ahead for 4 more time period in order to determine the activity's size.
But the code actually takes number 4 subtracted by 5 (which is the current time period of the current activity) and that yield -1.
Therefore, user does not get any period to look ahead.
The trick is to set TDAT(LA) big enough so that its interpreted LOOKAHEAD time period (say 9) minus 5 will be 4, which shoots to the number the user really meant at the first place until the end time period of the simulation horizon.
KeyWords
TDAT
LOOKAHEAD
LA
MRP
Keywords: None
References: None |
Problem Statement: Users may experience error messages indicating missing tables or sets when starting MIMI Configured Applications (CAPS) for the first time after installation. | Solution: With the release of MIMI Family 4.0, the MIMI Configured Applications (CAPS), such as Demand Manager, Distribution Scheduler, Inventory Planner, Plant Scheduler, Power Planner and Supply Planner, have been redesigned to utilize shared libraries of functionality. The CAP Libraries consist of Aspen MIMI cases which contain groups of related features. Current CAP Libraries include General Methods, Data Management, Data Viewer and Planning Framework.
The installation process for the MIMI Configured Applications (CAPS) assumes a default location for the shared libraries, "C:\Program Files\AspenTech\Aspen CAPS\Shared Libraries". A zipped file containing the shared library case will be installed in this default location, unless moved to a different directory.
The MIMI CAP stores the location of the shared libraries in the $TCASES and $CASES tables of the configured application case. In order to allow the CAP to locate the shared libraries in non-default locations, the user should edit the $TCASES and $CASES tables in the CAP to indicate the actual path to the shared libraries.
KeyWords
MIMI Configured Applications
MIMI CAPS
CAPS Libraries
shared libraries
$TCASES
$CASES
missing sets
missing tables
Keywords: None
References: None |
Problem Statement: How to print the planning board in color using the WINSHOT command. | Solution: Open any case.
Press F3 for the command line.
Type: winshot main2 pb.jpg
The print results will be located at \AspenMIMI\cases\pb.jpg.
Open the pb.jpg file and print it to a color printer.
Explanation of parameters:
winshot - The MIMI command
main1 - The graph or dialog you want to print from MIMI - the name is always on the top of the window screen. pb.jpg - The file name you created for the picture to save into and the file extension can be bmp, jpg, or png.
For further details, see the MIMI on-line help files for the WINSHOT command.
KeyWords
WINSHOT
jpg
bmp
png
Keywords: None
References: None |
Problem Statement: Rules to be respected when using the MIMI COPY command | Solution: If a table already exists in a model, there are some rules which modelers need to comply with when updating it with the COPY command:
The rimsets of the table must match the rimsets of the source table in the source case file;
The rimset of the source table in the source case file must have non-zero code portion.
The rimset of the source table must have data in the source case file. In other words, it cannot be temporary.
The COPY command will fail if any of the above conditions is not satisfied.
In addition, if the rimset of the source table is temporary, the following error message will be generated if user attempts to COPY the table:
"M0692: Row set [name of the set] from stored case had no code portion".
KeyWords
COPY
M0692
CODE
TEMPORARY
CQ00187692
Keywords: None
References: None |
Problem Statement: We can enter non-numeric data in the NUMBER widget of the dialog. Why? | Solution: The NUMBER widget is a leftover from UNIX/MOTIF interface. This widget with that name exists only for compatibility purposes with old UNIX applications. However, Windows does not offer a NUMBER widget and therefore, the number widget is just a text widget. If you want to validate the entry as a number, then you should do it as part of the after procedure in a rule.
KeyWords
NUMBER
WIDGET
DIALOG
Keywords: None
References: None |
Problem Statement: Does MIMI/LISA module support the SAP R3 Release version 4.6B? | Solution: As long as SAP supports the 4.6b library, then the MIMI/LISA module should function properly.
KeyWords
LISA module
SAP
Keywords: None
References: None |
Problem Statement: How to transfer large MIMI cases using AspenTech's File Transfer Protocol (FTP) site? | Solution: Open a DOS prompt and change directories to where the MIMI case resides.
Type "ftp ftp.aspentech.com"
You will be prompted to type username and password.
Username: anonymous
password: your email address
At the FTP prompt, change the directory to pub\download
cd pub then press Enter
cd download then press Enter
Change to either bin or ascii mode depending on the type of file you are transfering.
Type BIN for binary and press Enter (Please note that all zipped files are binary.) or
Type ASC for ascii and press Enter
Use the PUT command and the filename to place the file at FTP site.
PUT (casename)
Once the file has been successfully downloaded, send an email to [email protected] to notify the support team. Include the incident number in the subject if applicable along with a description of your issue.
KeyWords:
Keywords: None
References: None |
Problem Statement: How is Cumulative Campaign Cost (CAMPAMT) calculated within table SRCINDF (M SEARCH algorithm)? | Solution: SRCINDF(*,CAMPAMT) stores accumulated lot size for activities in a search family (which is defined in SRCCMAN(FAM) pointing to a column in TYPE table).
For example, user has FAM A and FAM B, and on facility F, the 3 first activities belong to A and the remaining 2 activities belong to B. Lot sizes of the 5 activities are respectively 12,34,56,78,90. Furthermore, we assume all 5 activities go into search routine.
SRCINDF(*,CAMPAMT) calculation will be performed as followed:
0
--- Initialized to be 0, always.
12
--- The 2nd activity inherits from 1st activity's lot size since they are same family.
46
--- 3rd inherits the sum of first 2 activities (hence accumulated): 12+34=46
112
-- 12+34+56=112. Note that this activity is also the point of family switch, so reset CAMPAMT for subsequent calculations (in this case, to be 78)
78
--- Inherits from 4th activity. Note that since this is last activity, number 90 (5th activity's lot size) is discarded.
Keywords: None
References: None |
Problem Statement: I get an error message of "Load is restricted to authorized users only," when I try to load any cases. | Solution: This is due to the version of MIMI on the workstation. The version of MIMI installed on the machine is from the eSupply Chain Suite CD. There are several possible solutions.
The user is not authorized to use MIMI so he or she will be unable to open the case. Verify that the user is authorized to use MIMI. Please note that the user will be unable to access the cases even if the cases are located on a local hard drive.
The workstation is not connected to the network and cannot reach Aspen Framework on the Aspen License Manager server. Verify that the workstation is connected to the network.
*Recommendation: If you are using MIMI exclusively and often work offline, then the best thing to do is to uninstall the version you have presently and install MIMI Classic as it will not use Aspen Framework and allow you to access the cases.
KeyWords:
Keywords: None
References: None |
Problem Statement: Under certain circumstances, MIMI users get an error message "Unable to improve position" when attempting to run command CAPSEQ (reschedules an existing batch or finite number of batches) to a better place in the schedule. | Solution: One of the reasons of having this error message is due to the float number rounding issue: Sometimes in customer case files, the shutdowns around the activity (say, activity A) may have the same JITB time as their own AS/ST time (Actual Start / Setup Time). When CAPSEQ is run, it initializes A's new start time to be the actual start time of the activity it is supposed to insert before (say B). Later, A is running a JITB check against B, but it happens in this case that B's JITB is the same as B's AT, or A's new ST, and the check procedure therefore runs into randomness -- Say X = Y + [very small number] and Z = X - Y - [same very small number], then Z is not always 0 in reality; sometimes it can be a very small positive number, sometime a very small negative number. One workaround for users is to tweak the activities (those activities that encompass the activity to be CAPSEQed) JITB to be a little later than the AT. \
KeyWords
CAPSEQ
JITB
Keywords: None
References: None |
Problem Statement: How can I use the $INFMAC and $INFMAR sets? How are they populated? | Solution: $INFMAR and $INFMAC contain infeasibility rows/columns when an infeasible problem is formulated. These tables should be automatically populated when using OPT in MIMI 5.0 and earlier versions. When using XPRESS, only MIMI 5.0 will populate these tables automatically, otherwise, the user need to manually open the $INFMAR and $INFMAC sets.
KeyWords
Keywords: None
References: None |
Problem Statement: Is there a limit on case file name length?
Yes, case file names can only be up to 14 characters in length. Anything more than 14 characters will return a message "Invalid case file name or directory" or "Case File Open Failure - Unable to Locate or Read Case File" depending on the Aspen SCM version. | Solution: Limit case file name to 14 characters or less.
Keywords: SAVE
SAVE AS
CASEFILE
FILENAME LENGTH
CASEFILE NAME LENGTH
ERROR OPENING CASE FILE
CANNOT OPEN
References: None |
Problem Statement: Honor Zero As Upper Bound (ZUPB) Parameter (in CLPS Table). Information of interest. | Solution: Recently the following question was raised:
"Is a blank considered the same as zero when ZUPB parameter is set to YES in the CLPS table ?"
The following explanation is answering this question and is of interest for further use.
ZUPB (Honor Zero As Upper Bound) is a parameter in the CLPS table that forces a zero value as a zero upper bound. There may be four possible cases when setting the ZUPB parameter:
The value of the ZUPB entry in CLPS is filled with "YES".
The value of the ZUPB entry in CLPS is filled with "NO".
The value of the ZUPB entry in CLPS is filled with others (a BLANK, or ANYTHING ELSE).
There is no ZUPB entry in CLPS at all.
In case 1, MIMI/LP will use a "zero value" as a zero upper bound. This is the ONLY CASE where MIMI/LP will be forced to use a "ZERO" value as a zero upper bound. In the rest of cases, the ZUPB parameter will all be defined as "NO", either explicitly or implicitly. Therefore, MIMI/LP will use +INF as a column vector upper bound of zero.
The upper bound is determined by MIMI according to both the value of the ZUPB parameter in the CLPS table and the setup of MAX in the POLI table. If ZUPB is "NO", a blank or zero entry of MAX in POLI assumes an INFINITE upper bound. If ZUPB is "YES", a blank or zero entry of MAX in POLI means a ZERO upper bound, instead of an INFINITE upper bound Notice that blanks and zeros in POLI table have the same meaning for GEN.
Should you need additional information, please consult Online MIMI Help and MIMI Linear Programming User Manual.
Keywords: None
References: None |
Problem Statement: How to fix the error message "Licensing information required to run MIMI is not available" | Solution: Description:
Creation Date: 18-Oct-2002 08:29AM
Applicable Version(s):
Multiple
Keywords: None
References: None |
Problem Statement: How to troubleshoot an error message "Case File Open Failure - Check File And Retry" | Solution: The error message is not specific, but rather a general statement. The physical memory of the machine can be insufficient for a MIMI case to open. Do the following test to verify the error message:
Run the case on another machine that has more memory, then open the case again.
Rebooting the machine can temporarly release used memory, but is a temporary solution. However, if the case opens without the error message then do a cas2dat and dat2cas to clean the case's wasted space.
Also check the paging file - set it twice as large as the actual physical memory size.
Open task manager to monitor the memory usage of the case.
Otherwise, contact MIMI support at [email protected] for further assistance.
Keywords: None
References: None |
Problem Statement: How can I bypass $LOAD$ post-load macro in Aspen SCM? | Solution: When loading a case file, the $LOAD$ post-macro is being executed. The $LOAD$ macro executes other macros (or rules or specific SCM commands) that run while the case file is being loaded. It can happen that one of those macros (or rules or specific SCM commands) launched by $load$, can not be executed, for some reason. In that case, SCM will get "frozen" and the application needs to be ended.
To avoid such "frozen" situation", a good workaround is to perform the following actions:
1. Open MIMI application.
2. Hold the CTRL button and open the case file.
3. This will bypass the $LOAD$ macro and the case file will open without any problem. The case file can then be modified as needed.
KeyWords
$LOAD$
Keywords: None
References: None |
Problem Statement: I want to convert a MIMI table or set data into text files for importation into another database. | Solution: Go to the set or table with the desired data.
Highlight all the cells (not the columns or row headers). After choosing all the data desired, right click and select copy.
Create a new text file by right clicking anywhere on the desktop and selecting new. Name the text file whatever you desire and then right click on the empty text file and choose paste. The data should appear in the text file.
Manually modify the file to your import routine's needs.
You should use comma delimited files, as manually setting each entry to fixed length will take a long time, length of time depending on the number of cells. All empty cells selected from the MIMI table or set will default to a setting of zero.
KeyWords
Keywords: None
References: None |
Problem Statement: How to create and send emails from within MIMI. | Solution: Sending emails can be useful, for example, to email bulk loading schedules to carriers. Here are two possible ways of implementing email sending.
Suggestion 1 - To do this you can use MIMI commands SYS or FORK, as MIMI gives you access to the DOS console. Follow the steps below:
Get a "batch eMail" program from your eMail vendor (i.e. a console SMTP email client, e.g. smtpmail.exe from the MKS toolkit).
You can also find one, for example, on a web site.
Put the email executable in the \Mimi\Bin folder or some other convenient place.
Get the documentation for the "batch eMail" program.
If that program needs a script:
Its documentation will tell you how to create the script.
Create a MIMI macro that creates the script.
Have the macro export the script to the hard disk and run the "batch eMail" program with the MIMI command FORK.
If no script is required, you will be able to send an email using a MIMI command similar to this: SYS SMTPMAIL -f from_email_adress -h name_of_smtp_host -s subject_of_email to_email_adress < full_name_of_file_to_be_sent
In this example, the console SMTP email client is smtpmail.exe while the meaning of the parameters to the program is self-explanatory.
Suggestion 2 - You can write an external program, for example using Visual Basic, that gets invoked by MIMI and communicates with MIMI via Active-X (MIMI/X). It creates and sends an Outlook message. To do this you need to have Outlook installed on your machine. You can find here attached an example scheme of such a VB program.
KeyWords
EMAIL
SYS
FORK
OUTLOOK
SMTP
VISUAL BASIC
Keywords: None
References: None |
Problem Statement: How can I set MIMI settings for each login account automatically? You may ask yourself this question, for example if you are using MIMI with Citrix, if you want to set the MIMI settings in order to see the MIMI windows in your model (graphs, dialogs, etc.) in an optimal way. Changing the MIMI settings manually for each user - by going to the "Options" / "System" menu -> "System Options" window - would take a very long time. | Solution: The MIMI system settings are saved in the registry. The solution is to make the settings for one user, the current user, export them to a file and then import those settings for the default Windows user. So, when any user logs in the first time, they get these MIMI settings. The registry file can also be used to reset the desired MIMI user's settings, just by importing them again. As usual, you must be extra careful in managing the registry, and always maintain backup copies. Also make sure that MIMI is not running during the registry import/export operations.
The HKEY_USERS section stores the settings for each user that has logged onto the machine. There is a tree entry for each user; if a user never logged into the machine, there will be no tree entry for it. When a user logs in, that user's specific settings are put into the HKEY_CURRENT_USER section of the registry.
Here is the detailed procedure:
Export MIMI settings from the registry into a .reg text file
Run Regedit from Start | Run...
Browse to HKEY_CURRENT_USER | Software | AspenTech
Highlight the MIMI key under AspenTech
Choose "Export Registry File..." from the "Registry" menu
Edit the .reg file so that the settings be attributed to the default user
Open the file with a text editor (e.g. Notepad)
Replace all occurrences of HKEY_CURRENT_USER with HKEY_USERS\.DEFAULT
Import MIMI settings from the text file to the default user
You can either:
Run Regedit from Start | Run...
Choose "Import Registry File..." from the "Registry" menu and browse to your .reg file
Close Regedit
Or:
Double click on your .reg file from Windows Explorer
KeyWords
MIMI SYSTEM SETTINGS
MIMI SYSTEM OPTIONS
REGEDIT
WINDOWS REGISTRY
Keywords: None
References: None |
Problem Statement: After installing MIMI, the following error may appear, "Cannot find WINRPC32.dll". This problem occurs when the "Force all core components" box is not checked at the end of the installation procedure. | Solution: To avoid the problem:
Follow the procedures to uninstall MIMI. Note: Do not uninstall ALM.
Reboot.
Install MIMI.
Before you click on the "Start Installation" button on the last installation screen, be sure to check the "Force all core components" box.
Reboot after the install complete.
Test MIMI.
Should the error persist, contact the MIMI helpdesk at [email protected] for further assistance.
KeyWords:
WINRPC32.dll
INSTALL
LOAD
Keywords: None
References: None |
Problem Statement: Starting MIMI on UNIX is returning the following message: "casebank.dir not found or in use". | Solution: If CASEBANK.DIR used to work, then it is possible that some priviledges on the MIMI directories were lost.
There are UNIX commands on how to check user's permissions on the MIMI directories:
ls -lrt command will list the files or directories in details including their permissions.
CHMOD 777 <Filename>
(The CHMOD command with 777 will give the user the read, write, and execute to a file or folder.)
The users need permission to all MIMI directories. Double check and make sure that your permission or user's permission did not change.
KeyWords
CASEBANK MODE
CASEBANK DIR
CASEBANK.DIR
Keywords: None
References: None |
Problem Statement: According to communications from the US government, President George W. Bush signed the Energy Policy Act of 2005. This Act changed the time change dates for Daylight Saving Time in the U.S. Beginning in 2007, DST will begin on the second Sunday in March and end the first Sunday in November.
Does Aspen SCM address this change to the 2009 US Daylight Savings Time? | Solution: It has been determined that there is no impact of the change regarding the Aspen SCM family of products. The only area where there might conceptually be some issues, Aspen SCM Scheduling or the related CAPs, the system has never dealt formally with the details of time zones or daylight savings time changes, whether they occurred on the old dates or the new ones. Within any model, and therefore within any schedule, all dates and times are relative to the location of the model (or the system start date/time assigned to that model, if not the local one) and are uniform from there on out.
Keywords: time zone
day light savings
DST
References: None |
Problem Statement: Experiencing memory problems when running MIMI cases larger than 256 MB. | Solution: On AIX, there is a memory limit when running files larger than 256 MB. You need to modify the mimi executable program(s) in $MIMIHOME/bin. Assuming that you want to modify the executable program called mimi, go to the $MIMIHOME/bin directory and execute the following command:
/usr/bin/echo '\0200\0\0\0' | dd of=mimi bs=4 count=1 seek=19 conv=notrunc
You should make a backup copy of the mimi executable program before running this command.
To see that you were successful, run the following command:
dump -o mimi
On the last line of output from this command, under maxDATA, you should see 0x80000000. Before the executable program was modified, that value was 0x20000000.
If you are running in batch mode, you also need to modify the cmimi program.
KeyWords
Keywords: None
References: None |
Problem Statement: After a GEN, the following message appears at the bottom of the INFO window: Number of non-zero intersections: 54321 (67209 changed) What exactly does this mean and does it matter if these two numbers are different? | Solution: The first number is the number of actual non-zeros generated from GEN in the MATX. The 2nd number in parenthesis is not the actual non-zeros in MATX, but the number that was hit in the GEN command. (The 2nd number should always be larger or equal to the 1st one.)
KeyWords
Keywords: None
References: None |
Problem Statement: Between CAPs (Aspen Configured Applications) version 2004.3 and 2006.1 there was a change to the default setting of the SQL DATAEXPORT command in $LOAD$.
The previous setting was SQL DATAEXPORT 7.1
The current setting is SQL DATAEXPORT BATCH <batch number>
This causes a different level of checking by Oracle unlike when using the 7.1 setting, which results in multiple ODBC errors of the type shown below:
ODBC: called SQLExecute Failed.
SQLSTATE = HY000
NATIVE ERROR = 12899
MSG = [Oracle][ODBC][Ora]ORA-12899: value too large for column "ASCC_SO"."IMP_MODEL"."MODELTYPE" (actual: 20, maximum: 18)
For example you can see these results if you try to export from PS (Aspen Plant Scheduler) EO 2006.1 to ASCC (Aspen Supply Chain Connect) Oracle 10g with Oracle 10 ODBC. | Solution: For a very long time in the $LOAD$ of CAPs based models we set DATAEXPORT to 7.1
The DATA EXPORT BATCH is a newer feature, which enables batch mode, greatly increases the export speed. See the online help at SQL DATAEXPORT BATCH.
Enabling batch mode has the following costs though:
1. All table fields must be at least as large as the width of the Aspen SCM source table. For example, if your model's table has a C30 format, each field exported will be filled with trailing spaces up to 30. Every field in the database table then must be at least 30 or more.
2. All data exported contains trailing spaces up to the width of the Aspen SCM source table. In the ASCC database the text field type is VARCHAR, which treats spaces as significant. Therefore, for ASCC to be able to use the batch mode you would need to add stripping logic when moving the data.
3. The export will terminate with an error if any data truncation occurs.
Notes:
? The DATAEXPORT setting only applies to outbound data.
? Setting the DATAEXPORT to BATCH will override any prior setting of DATAEXPORT so the 7.1 mode gets turned OFF. This is important only if you want to turn the BATCH feature on and off. When turning the batch feature from ON back to OFF you will want to re-enable the 7.1 mode.
? The optimal batch size depends on various factors. A setting of 250 is a good starting point.
? This is not a Oracle 10g vs. some other version of Oracle problem.
Note that, in SQL Server database:
? If you create the field as CHAR NOT NULL trailing spaces will be insignificant.
? If you create the field as CHAR NULL and set ANSI_PADDING ON trailing spaces will be insignificant.
? If you create the field as VARCHAR and set ANSI_PADDING OFF trailing spaces will be truncated.
? In other cases we believe the trailing spaces will be significant. In that case you must add some post processing logic to truncate any trailing spaces.
You will need to do some testing to confirm the trailing spaces are not significant. Otherwise you have endless data match-up problems later.
Keywords: None
References: None |
Problem Statement: What rights do I need to install and run the request broker for Aspen SCM? | Solution: You need administrative rights on the workstation to correctly install the broker. This will allow the broker to start up as a service using the system account when you boot up your PC. Failure to install with these rights will result in the broker not working properly.
Keywords: None
References: None |
Problem Statement: How often should cas2dat and dat2cas be used for my Aspen SCM case files? | Solution: Before using cas2dat and dat2cas, its important to know what exactly they do. The purpose of cas2dat/dat2cas is to convert a binary file to character (then back) so the file can be transported to other operating systems. However, many customers do not realize the additional benefit to running cas2dat and dat2cas on a regular basis. These utilties not only remove wasted space from the case, but they also re-index the catalog of sets and tables. As a result, your case will run more efficiently.
Customer Support recommends that you perform cas2dat / dat2cas every day while the model is in development. Any time there are constant changes being made to the case, it's a good idea to include these utilities in your daily activities.
Once the case is in production, Customer Support recommends that you perform cas2dat / dat2cas on a weekly basis.
For more information on cas2dat and dat2cas, please reference the Aspen SCM On-Line help files.
Keywords: None
References: None |
Problem Statement: How to write date columns using MS SQL/Server 2000 | Solution: Enabling the TimeStamp feature will allow data to transfer with dates on MS SQL / 2000 Server. The following steps show how to add the TIMESTAMP ON feature:
Open the SQL Code and include the syntax to turn on the TIMESTAMP.
Type SQL TIMESTAMP ON; on the description field of the SQL table code.
The MIMI on-line help provides more example how to apply the TIMESTAMP feature.
KeyWords
MS SQL 2000
TIMESTAMP
DATE
SQL
Keywords: None
References: None |
Problem Statement: CPLEX OPT command is hanging MIMI | Solution: It has been discovered that MIMI sometimes hangs while running the CPLEX OPT command due to two corrupted files. These files are Q.PTR and CPLEXLIC.QRM located in the folder CPLEXLIC. Therefore if a MIMI user is facing such issue, he/she should obtain from MIMI support those two files and copy them into the correct directory. This should solve the issue.
Keywords: None
References: None |
Problem Statement: What causes the following error message "MIMIAS - MIMI V5.2 message mismatch with that of MIMI 6.2.6"? | Solution: This problem is due to an incorrect path. To correct this path, load MIMI and go to Options --> System --> Files --> System Files. The path for system files should be the same as the HOME directory with \BIN appended to the end of it. Make this change and test MIMI to see if the error goes away. If not, please contact the help desk at [email protected] for further assistance.
KeyWords
MIMIAS
Keywords: None
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.