question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: Disclaimer: Information on Automation and Extensibility Examples in the Model Library | Solution: HYSYS incorporates an advanced software architecture and Microsoft COM(R) technology to provide a component-based framework that can be easily customized, updated and maintained to meet changing user requirements. Options for tailoring HYSYS generally include:
Automation:
The use of third party tools such as Visual Basic or the HYSYS Macro Language Editor to programmatically run HYSYS.
Extensibility:
The creation of custom unit operations, property packages and kinetic reactions which become part of the simulation and function as built in HYSYS objects.
The automation and extensibility examples contained within the Knowledge Base Model Library illustrate how the object-oriented structure of HYSYS can be used to customize and extend the existing functionality of the software.
Note 1: The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released heritage-Hyprotech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use these examples. We invite any feedback through the normal support channel at [email protected].
Note 2: Before attempting to run any of the automation examples, ensure that you have the Visual Basic 5.0 MSVBVM50.dll and 6.0 MSVBVM60.dll run-time files installed in your Windows System32 directory.
KeyWords
Automation, Extensibility
Keywords: None
References: None |
Problem Statement: How do you correctly model a copolymer in a mixture that forms two liquid phases?
The copolymer component is modeled by a large hydrocarbon C36H74, with modifications for PLXANT-1 parameter 1 being set to -1e15 to make it non volatile, and with a user defined Molecular Weight and a user defined free energy of formation. With the POLYPCSF property method, the heavy component appears in the vapor output of a flash3 block.
This also happens if you use the database values of C36H74. | Solution: A copolymer should be modeled by at least two segments (not a conventional component). The properties of the copolymer (such as the molecular weight) should be calculated from its segment molecular weights and compositions.
When water exists in the mixture to form a second liquid phase, the PC-SAFT (not POLYPCSF) property method and the PC-SAFT databank should be used. The PC-SAFT parameters for the copolymer should be entered for its segments (PCSFTR instead of PCSFTM) and not for the copolymer itself. When using PC-SAFT (or POLYPCSF) there is no need to enter PLXANT-1 parameter for the copolymer to make it non volatile, the correct molecular weight calculated from its segments will guarantee it is non volatile.
The attached file, copolymerV71.bkp, is an illustrative example using PC-SAFT property method and PC-SAFT and SEGMENT databanks for modeling a copolymer system. The copolymer is defined by two segments, C2H4-R and C3H6-R and the segment compositions are 500 for each segment. PC-SAFT parameters available for conventional components are retrieved from PC-SAFT databank and for segments are retrieved from SEGMENT databank.
Keywords: None
References: None |
Problem Statement: Stream Flow Rate Multiplier | Solution: The attached case demonstrates a quick and easy way to multiply the flow rate of a process stream using a Tee and a Set operation.
The feed stream is fed to a Tee. There are two outlet streams. The first is to contain the multiplied flow rate of the outlet stream. A Set operation contains the factor by which you multiply the flow rate of the feed stream and transfers the flow rate to the first outlet stream of the tee. The second outlet stream from the Tee will close the mass balance.
Note: If the flow multiplier is greater than 1, this second stream will be a dummy stream with negative flow. (It is not sensible to connect operations to the dummy stream.)
Keywords: stream flow rate multiplier
References: None |
Problem Statement: Is it possible to change heat to work? | Solution: This can currently only be done with a User2 block. See the attached example file.
To run the example, put all of the files in one directory.
Fixed in Version
In v7.0, it will be possible to change heat to work in a ClChng block.
Keywords: None
References: : CQ00318539
Contributed by Stefan Pofahl |
Problem Statement: Is it possible to have a reaction in an RStoic with a nonconventional component and other conventional components? | Solution: Yes, it is possible to have reactions between components in different substreams.
In the attached example (NC-comp-drier100.bkp), all of the water in the nonconventional (NC) component wood pulp is removed in an RStoic that acts as a drier.
The wood pulp is specified using GENANAL component attributes. The fifth element represents the moisture in the wood pulp. In this example the moisture is specified as 14%. See Solution 102341 for more details about how to specify wood pulp.
In the reaction in the RStoic block, the nonconventional component (PULP) is specified on a mass basis, and the conventional component (WATER) is specified on a mole basis.
Hence, the following reaction is used:
1 CONVERSION 18.01528 PULP --> WATER
The stoichiometric coefficients is set as 18.01528 because water has a molecular weight of 18.01528 g/mol.
The fractional conversion is set to 0.14 (14%) because this is the amount of wood pulp that is water.
The component attributes for the wood pulp must also be specified in the block. Since all of the water is removed from the wood pulp, element 5 is set to 0. With element 5 set to 0, the total of all of the elements is no longer 100 percent. Aspen Plus will automatically re-normalize the values for the other elements and print a warning message to alert users to this fact.
It is possible to use a calculator block to set the fractional conversion to be equal to the amount of moisture specified as Genanal element 5 and to re-normalize the proportion of the other elements for the product stream. See the attached file "NC-comp-drier100-withcalculator.bkp".
Keywords: None
References: None |
Problem Statement: 3-phase - Acetic Acid separation column. | Solution: An entrainer (Ethyl Acetate) is used to aid the separation of water and Acetic Acid.
The UNIQUAC property package with the Virial option is used. This ensures that the dimerization of acetic acid and water in the vapor phase is properly modeled.
The Sparse Continuation solver is used as we have a three phase condenser in this system.
If the column does not solve for you; simply stop the column solver, press the "reset" button and then re-run the column.
See the attached case for more details.
Keywords: column, 3-phase separator, acetic acid, Ethyl acetate
References: None |
Problem Statement: How do you enter performance curves for a Pump? | Solution: There are three options for entering performance curves for a Pump: (1) Tabular data, such as Head vs. Flow points (2) Polynomials, i.e., coefficients for a Head = a + b*flow +c* flow2 + d*flow3 correlation, and (3) a User subroutine in Fortran.
1. In the Model area of the PUMP Setup Specifications sheet, select Pump.
2. In the Pump outlet specification area, select 'Use performance curve to determine discharge conditions' option.
In the Efficiencies area, input the Pump Efficiency and/or Driver Efficiency (or use the defaults).
Note: Efficiencies can also be added as tabular data or polynomials. If you use this option, do not enter a value in the Pump Efficiency field.
3. Navigate to the PUMP Performance Curves Curve Setup sheet. Choose the appropriate curve format: Tabular data, Polynomials, or User subroutine.
4. Choose the Performance (i.e., Head) and Flow variable (vol. flow) variables and the number of curves: a single curve at operating or reference speed, or multiple curves at various speeds.
5. On the Curve Data sheet, enter the tabular data:
Or, polynomial coefficients:
The attached example shows two pumps -- each with a single performance curve at operating speed. The TABULAR pump is characterized using Head versus Volumetric Flow data while the POLYNOM pump uses coefficients.
Keywords: Pump, performance curves, head vs. flow, tabular, polynomial, compressor
References: None |
Problem Statement: Sample file for Biofuels (Biobutanol) Hysys Process Modeling for ABE Fermentation Technology | Solution: In attached report, Aspen Hysys example how to model ABE fermentation process is given. This report is only intended to give you a starting point. User should carefully examine the parameters and flowsheet
Keywords: Hysys, fermentation, biobutanol.Example, Sample
References: None |
Problem Statement: Real Separator (RealSep) Extension Unit Operation (created in C++) | Solution: Attached is a sample unit operation extension which demonstrates how to model a separator that models liquid and vapour phase carryover (molar basis). It was created using C++.
Note: These examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released heritage-Hyprotech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use these examples. We invite any feedback through the normal support channel at [email protected].
KeyWords
C++, RealSep, Real separator, non-ideal separator
Keywords: None
References: None |
Problem Statement: How do you show equipment convergence status in Aspen Simulation Workbook from Aspen HYSYS simulation? | Solution: In Aspen Simulation Workbook (ASW) there is no variable to report the equipment convergence status within HYSYS simulation. The example case here is to illustrate how this can be implemented in ASW.
In most cases the status of product stream(s) of connected any unit operation indicates if the unit has been converged or not. If the product stream has been specified and the feed stream calculated (for example, a recycle operation) then the status of the feed stream should be considered.
The status information can be generated in a HYSYS spreadsheet using a conditional statement, for example,
@if(B2==-32767, "Not Solved", "Solved")
Here the value -32767 represents an empty value. If the molar flow in a stream is empty then the connected unit is not solved.
In the attached HYSYS simulation a spreadsheet is created to generate status for all the unit operations in the PFD.
A screenshot for the spreadsheet is given below.
The status fields can copied to the ASW Organizer and the results can be presented in Excel. See the attached Excel file. A screenshot for equipment status in Excel ASW is given below.
Keywords: ASW, Equipment Status
References: None |
Problem Statement: How does one import data from MS Excel into a source? | Solution: The attached files include two examples which import source data from MS Excel into Aspen Flare System Analyzer.
In the first example, all scenario source data is in one worksheet; in the second example, each scenario has its own worksheet.
Additional information regarding the second sample can be found in Aspen Flare System Analyzer
Keywords: MS Excel, definition file
References: Manual.
There are several items which require attention:
1. You need uncheck Import as New option when you import the data into existing network.
2. Your composition of each source must add up to 1 (not 0.999).
3. You want to trigger Composition basis when you import molecular weight or composition (0 = MolWt, 1 = Mole fraction, 2 = Mass fraction). |
Problem Statement: The old, familiar ".lst" reports of PIMS are based on obsolete technology. They cannot keep up with the new features of PIMS. So, the ".lst" reports will be discontinued sometime between the release of PIMS versions 16 (2004.1) and 17 (2006). | Solution: PIMS currently features the ability to create HTML reports, ".txt" text reports (which are relatively new), and the classic ".lst" reports.
PIMS will officially retire the LST report files after the PIMS 16 release. Equivalent and significantly improved functionality is available in either the HTML reports or the ".txt" reports that are generated.
KeyWords
text
.lst
LST
report
reports
Keywords: None
References: None |
Problem Statement: Is Dortmund Databank supported in Release 10 of Aspen Plus? | Solution: No. Customer wishing to continue to use apddbi to retrieve data from the dortmund databanks must use it with Release 9.3. Data also cannot be migrated.
The DETHERM Interface in Aspen Plus 10 replaces the Dortmund Interface. The DETHERM database is accessed via the Internet. Individual data sets can be purchase. The database can be queried without an account; however, users must register before they can purchase data. See Solution 102256 for more information about using the DETHERM Interface.
KeyWords:
Dortmund Databank
Keywords: None
References: None |
Problem Statement: If you are using AspenIQ with TDC, there is a mapping inconsistency in the LBU section.
ISSUE:
The AspenIQ TDC user guide suggests that .LBIASNEW AND .PLBIASNEW be mapped to the .LBIASNEW(31) of the inferential point. IF you have done this mapping then when a Lab value fails a validity check (for instance, an ROC check), the .LBIASNEW gets set to zero and passed on .PREDBIAS of the inferential. This could cause a big change in the inferential value depending on how big the .PREDBIAS was to start with.
Please read the following for a detailed explantion of how .PREDBIAS gets set to zero. Remember that the .LBIASNEW gets filtered into the .PREDBIAS when lab updates are used.
First you need to understand that all tags that are connected to the same DCS point share the same memory region for the value. In other words both the LBIASNEW and PLBIASNEW were using the same memory region to store their values. So here is how the problem could occur.
The validation of the lab sample fails and PLBIASNEW is set to zero.
The LBIASNEW is not updated since no lab value passed validation. (It is around 15)
LBIASNEW is written to the common buffer. It writes a 15.
PLBIASNEW is written from the program's memory to the common buffer. It writes a 0.00 on top of the 15.
Later, the PR module runs and it grabs the current value of LBIASNEW from the common buffer. It grabs a zero! | Solution: In the IQF file, set the .LBIASNEW keyword to either 'local' or 'none'. Leave the .PLBIASNEW mapped to .LBIASNEW(31). This will prevent this problem.
Note: Developer is updating his AspenIQ user guide and the updated version will be available soon.
KeyWords
Aspen IQ, TDC, LBIASNEW, PREDBIAS, Lab Update, Bias Update, lab value
Keywords: None
References: None |
Problem Statement: User starts up Aspen IQ and because the license manager has not been started, licensing cannot be checked out and the application goes to DEMO mode which does not allow saving of any files created. Problem is, the application does not always let you know that is the mode you are operating in. It has been determined that if the described change to the registry is made, the license manager and associate processes start when needed and product is properly licensed and operates as expected. | Solution: Use regedit goto:
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sentinel
Add a new String Value
Group "Extended Base"
KeyWords:
Aspen IQ Model, model, ALM, License Manager
Keywords: None
References: None |
Problem Statement: Is it possible to use custom Aspen Custom Modeler models in Aspen Plus V7.3.2 without installing V7.3?
I cannot find the ?apmodelscatalog.xml? file that is normally installed in the C:\ProgramData\AspenTech\AES where the location of the .dlls needs to be entered. | Solution: No. You need to install Process Modeling (Aspen Plus) from the V7.3 DVD before you can run exported ACM models in Aspen Plus V7.3.2.
The ?apmodelscatalog.xml? file is installed as expected after installing ACM V7.3. The location of the apmodelscatalog.xml depends on the operating system.
? Windows 7 and Windows 2008 server R2 x64: C:\ProgramData\Aspentech\AES
? XP and Windows 2003 Server R2 (x86) : C:\Documents and Settings\All Users\Application Data\Aspentech\AES
Keywords: configuration, installation, compatibility
References: None |
Problem Statement: Using a non-English operating system, when we try to compile a Fortran file with "aspcomp" in the Aspen Plus Simulation Engine window, we obtain this warning:
ASPCOMP: Warning! Intel Fortran runtime library libifcoremd.lib not found in %LIB%
ASPCOMP: Warning! Intel Fortran runtime library is needed for Dynamic Linking.
...and linking is not successful. | Solution: Users on non-English versions of Windows may need to set the language in Microsoft Visual Studio to English instead of Use Windows default.
Keywords: None
References: : CQ00380192 |
Problem Statement: COLSUM is displaying different summation results between the floating tables and the integer tables. | Solution: At this time, use the integer table and not the floating table for large numbers.
Analysis: MIMI tables have a limitation of 7 digits, therefore, even if you try to increase the format field at the set attribute table, it will automatically reset to 7 digits or less. However, our development staff tested the integer table up to 10 digits and the summation returned the correct values. Unfortunately, the display is also limited to 10 digits.
Note: This is not a COLSUM bug, rather a limitation on the floating table and display.
KeyWords
Keywords: None
References: None |
Problem Statement: Sentinel System Driver Error 1406 | Solution: Description: This error can occur when the Sentinel System Drivers are installed after HYSYS on the Windows 2000 operating system. When HYSYS installs the drivers, it also starts them. When drivers are started, they access information in the registry. However, in accessing the information, some keys are left open. Then, when the drivers are installed by the stand-alone installer, its attempt to write information to the registry is blocked and an error message is displayed.
Workaround: This warning message should not be cause for concern because the drivers installed with HYSYS and those installed with the stand-alone installer carry the same version number. The required information is already present in the registry. When prompted with this error, just click on "Ignore" and continue on. The installation may re-start, in which case the error will come up again. Click on "Ignore" again and the installation should go to completion.
Keywords: known issues; slm; driver; 1406
References: None |
Problem Statement: On January 31, 2001, the CPLEX license codes embedded within MIMI expired. What does this mean to our customers?
If you are currently running CPLEX, the license is perpetual and will continue to run. However, if you attempt to install CPLEX after this date you will experience a licensing error like the one below.
Error 32104: Licensing problem: License code has expired. | Solution: Under NT, you need to do the following:
Open a session under the MS-DOS shell.
Change the directory to your MIMIHOME value, in most cases, MIMIHOME will be C:\MIMI\bin.
Type the following: instlcpx 41-37-70-B5-43-09-B9-8E-8E-98-94-1E-87-E5 c:\mimi\
Run MIMI again and test the CPLEX optimizer
Notes:
This code can be used to relicense CPLEX until March 3, 2007.
If the "instlcpx" statement wraps the text when you copy it to your DOS prompt, it will not work. You will need to type the statement in by hand.
If you are running UNIX, you can have a look at tech tip 105109 - "How to install CPLEX licensing under the UNIX environment".
KeyWords:
CPLEX
Error 32104: Licensing problem: License code has expired.
INSTLCPX
Keywords: None
References: None |
Problem Statement: The units for Henry Parameters on the Binary Input forms should be locked to what is used.
If the parameters Henry/2, Henry/3 and Henry/7 are NON-zero, the absolute temperature units should be displayed that are used.
If parameters from the databanks are loaded the actual units used should be displayed in case Henry/2, Henry 3 and Henry/7 are NON-zero.
If the user enters parameters and he enters a non-zero value for any of these three parameters, the units should switch to show the absolute units used. | Solution: It is very nice if unit can be consistent with value used in the parameters. It is not for Henry parameter only; also for many other parameters. The elements, which determine the unit setting, are different from each parameter.
For example, in Henry parameters, if the value of Henry/2, Henry/3, or Henry/7 is non-zero, the temperature should be set to R or K depending on unit originally used (e.g., F or C), and the value of Henry/5 and Henry/6 (TLOWER and TUPPER) should be changed with the unit change. In NRTL parameters, if the value of NRTL /3 or NRTL /7 is non-zero, the temperature should be set to R or K depending on unit originally used, and the value of NRTL /11 and NRTL /12 (TLOWER and TUPPER) should be changed with the unit change.
Fixed in Version
The best way to implement is to create a table for each parameter and list elements that should make the unit change. A semantic will be used to call the table to set the correct units. Since the implementation is very extensive, thus, we need to defer it to a future release.
Keywords: None
References: CQ00205262
KeyWords |
Problem Statement: In Aspen Plus 12.1, some files will run and complete without any problems; however in 2004.1 and higher,
you will get an error message about missing CPIG and the simulation will stop.
The error message will be something similar to the following:
*** SEVERE ERROR IN PHYSICAL PROPERTY SYSTEM
IDEAL GAS MODEL HAS MISSING PARAMETERS:
CPIG/1ST ELEMENT (DATA SET 1) MISSING FOR COMPONENT A1
****PROPERTY PARAMETER ERROR
ERRORS ENCOUNTERED IN CALCULATION OF IDEAL GAS PROPS FOR
HIG,DHIG
PLEASE FIX THE ERRORS, RE-INITIALIZE, AND RUN AGAIN.
If you use Tools/Retrieve Parameter Results, you will see that default values for CPIG are retrieved.
Why does it use the values in 12.1, but not in 2004.1 ? | Solution: If a component has no ideal gas heat capacity parameters in any of our the databanks then
a default value CPIG should not be used since this could lead to incorrect enthalpy calculations.
In 12.1 and 2004, there was a bug in the code that checks for missing ideal gas heat capacity (CPIG) parameters. For missing parameters such as these, the system should issue a severe error. However, this bug caused the severe error to be bypassed. The system default values for ideal gas Cp was used which allowed the simulation to continue. However, the results for ideal gas heat capacity for this component and any other properties calculated from this result will not be good. This is a bad problem since users might be getting bad answers but would not even know it.
In 2004.1, we fixed this bug which is why you see the severe error.
The solution is to give a better estimate of the ideal gas heat capacity (CPIG) parameters.
Keywords: CPL
References: : CQ00225734 |
Problem Statement: User defined dynamic stream initialisation not functioning properly. | Solution: Description: The Stream Initialisation option within the Dynamic Initialisation feature does not currently allow the user to specify the initialisation conditions. These are being taken as the current stream conditions and composition.
NOTE: The Dynamic Initialisation view have been made more clear in more recent versions of HYSYS.
Keywords: known issues; Dynamic Initialization; Dynamic Initialisation
References: None |
Problem Statement: At the present time, the Amines property package cannot properly handle zero flow of the following Amines components: H2S, CO2, DEA, TEA, MDEA, DGA, or DIPA. This is due to the calculation engine used in the Amines package, which is supplied by DBRobinson. | Solution: Workaround: The workaround is to ensure that if there is zero flow of any of the following components anywhere in the simulation: H2S, CO2, DEA, TEA, MDEA, DGA, or DIPA you will need to remove that component from the component list in the fluid package.
Keywords: known issues; amines; amsim
References: None |
Problem Statement: If the user has selected Field units and added a Workbook table inside the column environment, HYSYS will crash upon re-entry into the column environment after the case has been reloaded. | Solution: To recover the case, complete the following steps:
1. Delete the HYSYS.prf file, located inside the default HYSYS directory.
2. Reload HYSYS and the offending HYSYS case.
3. Ensure that the SI unit set is selected.
4. Enter the column environment and delete the workbook table.
5. Exit the column environment and change the unit set from SI to FIELD.
To prevent this problem from occurring, do not add workbook tables to the column PFD if the FIELD unit set has been selected.
Keywords: known issues, crash; column; tables
References: None |
Problem Statement: I just copied some numbers from a MD (Multi-Dimensional) table to another MD table. These are character tables (being MD) and contain numbers. The numbers are decimals <<< 1 in the source. After the paste, all numbers have their decimal points moved to make them > 1. | Solution: If you copy-and-paste numeric data into character tables, you may get completely wrong results and not notice. You may be copying thousands of numeric data elements and not realize that some of them were converted to scientific notation and then truncated. MIMI tries to convert the numbers to scientific notation and then truncates them in the destination table. This is especially an issue with the CAPs, which define all import data as character MD tables.
Do not ever copy scientific notation into a character table if it all could not fit. Rather default back to the numeric representation and let some decimal places get truncated.
The example below refers to numeric values copied from a source table into a C6-format destination table. Row 1 shows the results of a wrong copy&paste, row 2 shows how the copy&paste should be done.
Source values --> Values in editor --> Values after paste
.000123456 1.23456E-4 1.2345
.000123456 1.23456E-4 .000123
KeyWords
COPY AND PASTE
TABLE EDITOR
MULTI-DIMENSIONAL TABLES
Keywords: None
References: None |
Problem Statement: Problems Depressuring Pure Components | Solution: Description: There is a flash problem when depressuring pure propane. The pressure of the system rises to the relief pressure almost instantaneously without having any pressure build-up before the relief pressure is achieved.
Workaround: The workaround for this defect is to add a very small amount of impurity. In the case of propane, adding a 0.0001 mole fraction of C2 or iC4 will show a reasonable pressure build up before the relief pressure is reached.
Keywords: known issues, depressuring, pure components
References: None |
Problem Statement: PDA devices interfere with HYSYS security keys on the Serial port. -- Serial Port Keys are not Recognised.
Cause:
Most PDA (Palm, Visor, RIM, IPaq) syncronization software will reserve at least one serial port on the computer for exclusive use with the PDA. If the Serial port key happens to be attached to the COM Port that is in use by the Sync software, the security key will not be recognised by the Hyprotech SLM system and the product will fail to run. | Solution: 1. If more than on COM Port is available, place the serial key on the second COM Port.
2. If feasible, use the Infrared Port to Syncronize the PDA and turn off the Serial Port Syncronization Option.
3. Upgrade to a Parallel Port hardlock key or USB harlock key. The USB key will requre the use of Windows 98SE, WinME, Windows 2000, or Windows XP.
Keywords: PDA, SLM, KNOWN ISSUES
References: None |
Problem Statement: There is a problem with the formatting of the specsheet printed by the "Compositions" workbook. When you set it up to show the component LV rates, the two sides of the "Name" text overlap ("Comp Volume Flow(NBP[1]xxx" and "barrel/day"). This renders the component name unreadable.
You can reproduce this by loading our Crude Column example, then adding "Component Volume Flows" for all components to the Workbook. Then select Print Datasheet. | Solution: Use one of the extensions on the support website that will allow you to transfer HYSYS text to Excel. Alternatively, you may use the more desirable "Print Text to File" or "Copy With Labels" options and open/edit in Excel.
Keywords: known issues; printing
References: None |
Problem Statement: Relief valve in Dynamic Depressuring Utility gives inconsistent results | Solution: Description: When using the Relief Valve, the utility may give inconsistent results from one run to the next under certain circumstances. The problem manifests with a relief valve with a large area and a set pressure close to the relief pressure. This causes the valve to open slightly and continuously (chattering), which will cause inconsistent results in the peak flows calculated through the valve.
Keywords: known issues, relief valve, dynamic depressuring
References: None |
Problem Statement: In the DPO top menu, under EDIT, the MapBuilder option is greyed out. | Solution: The MapBuilder feature requires the presence of Microsoft MapPoint software. This is a supporting third-party software similar to how PIMS uses Excel. Some companies find they have already licensed MapPoint for other purposes and can easily make a copy available for use with DPO. Others will need to purchase the software if they would like to use the MapBuilder feature of DPO. MapPoint is a relatively inexpensive software to purchase (approx. $300 in the U.S. at an electronics store).
KeyWords
MapBuilder
MapPoint
Keywords: None
References: None |
Problem Statement: You will encounter this problem only when you have the experience mentioned below:
There is an older version of an HTFS program (e.g. PIPE 5.1) installed on your computer,
You install HYSYS or any other AspenTech products that uses COMThermo, and then,
You uninstall the HTFS program.
When you try to run any of these newly installed programs, you will encounter an error message indicating "COMThermo Flash Failed OR Flash cannot be carried out at specified conditions. - HResult returned 80070057"
This is due to a defect in the older versions of HTFS programs which removes the registry entries relating to COMThermo during the uninstallation process. | Solution: Download the zip file thhysysflash.zip. The zip file contains one file called thhysysflash.reg.
To download the file right mouse click on the link and use the "Save Target As" option.
To update the registry open the zip file and double-click on the file thhysysflash.reg, following any prompts provided.
KeyWords
COMThermo, HTFS, install, uninstall, registry
Keywords: None
References: None |
Problem Statement: For Equilibrate-Column and Wash-Column operations, specifying the amount drawn from tank in bed-volumes gives incorrect results. | Solution: Specify amounts in units other than bed-volumes.
KeyWords:
Equilibrate Column, Wash Column
Keywords: None
References: None |
Problem Statement: Product composition and amount are incorrect if the final product stream is created by Transfer Through Inline Filter opertaion. | Solution: Replace the Transfer Through Inline Filter with a combination of Filter-In-Place and Transfer operations.
KeyWords:
Transfer Through Inline Filter
Keywords: None
References: None |
Problem Statement: After using Data Regression for solubility modeling to regress the equilibrium constants for salt precipitation reactions (K-SALT) or equilibrium ionic reactions (K-STOIC), the parameters were not brought back onto the Chemistry forms even though "Copy results onto Parameters forms" was checked for Regression cases.
Cause
Chemistry results are not considered property or interaction parameters since they are not in the Properties\Parameters folder; hence, they are not brought back onto the forms. | Solution: Copy the results by hand onto the Chemistry forms.
Fixed in Version
This item will be considered for a future release.
Keywords: None
References: : CQ00208396
KeyWords
solubility modeling
drs
KSALT
KSTOIC |
Problem Statement: The following error may be encountered when opening an Aspen Dynamics file or using the Send To command -- procedure precall failed for pFlash2_par. The simulation will not run. | Solution: After opening the simulation in Aspen Dynamics, change Simulation -> Globals -> PropMode form Local to Rigorous.
Attached find the Aspen bkp file, dyn file, and appdf file. If the bkp file is opened in Aspen Plus and the Send To command is used, the Aspen Dynamics simulation will not run. The change has been made in the attached Aspen Dynamics file which solves properly.
Note that the .appdf file supplied with this example only works with Aspen Dynamics 10.2. You need to recreate the .appdf file to run this example in a different version of Aspen Dynamics. Please see above referenced solution 104531 for information on how to do this.
KeyWords:
dynamics
GlobalPropMode
Keywords: None
References: None |
Problem Statement: For Aspen OnLine projects involving large models (e.g., an Equation-Oriented (EO) model with more than 380,000 variables), offline to online may fail because the default value for the following registry entry isn't big enough. | Solution: WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Use Registry Editor to increase the MaxLocksPerFile value under the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0 To do so, right-click the MaxLocksPerFile value, click Modify, click the Decimal option, increase the Value Data from 9500 to some higher value (e.g., 20,000), and then click OK.
Note that this method changes the Windows Registry setting for all applications that use the Microsoft Jet database engine version 4.0.
For Windows server 2008 64 bit OS registry location is:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Jet4.0
KeyWords
Keywords: None
References: None |
Problem Statement: For Aspen Dynamics simulations with a single component and a pipe model, the simulation may not converge even in the initialization mode. The error message states that the liquid viscosities are too high. | Solution: This has been fixed in version 10.2 update 1 and later releases. The workaround for previous versions is included below.
The cause of the error message is a setting in the Aspen Plus Pipe model. When running a single component in the pipe model, Aspen Plus issues a warning stating that a heat duty must be specified or set the Flash Options --> Valid phases to single phase. If the user changes the Valid phases to single phase, then the warning is not present, BUT this causes the error in Aspen Dynamics. Ignore the warning in Aspen Plus. The Aspen Dynamics simulation will run properly.
KeyWords:
pipe
Keywords: None
References: None |
Problem Statement: Effect of unresolved colinearity on DMCplus control performance is investigated by M Harmes. Mike offers RGA analysis insights and suggests guidelines for step testing and subsequent modelling which significantly improves control robustness. | Solution: M Harmse discusses DMCplus control performance of ill-conditioned systems, and offers design suggestions.
KeyWords
DMCplus, DMCplus Model, colinearity, ill-conditioning, modelling, RGA
Keywords: None
References: None |
Problem Statement: DMCplus Composite .ini and .ccf Timing Guidelines | Solution: CLPTIME (in the .ccf) is the time-out tolerance for each individual controller and it will vary for each of the tiers (or order). The CLPTIME values used are based on a controller execution interval of say one minute.
The guidelines are as follows:
1st tier CLPTIME = GCTIM + 3 sec
2nd tier CLPTIME = 1st tier CLPTIME + 5 sec
3rd tier CLPTIME = 2nd tier CLPTIME + 5 sec
GCTIM
CLP get time in seconds (in the .ini). Typically set as [(Max CTOFF - Min CTOFF) + 5 sec].
PCTIM
CLP put time in seconds (also in the .ini). Typically set as [GCTIM + 5 to 10 sec]
KeyWords:
DMCplus, Composite, CLP, User's Guide, Documentation
Keywords: None
References: None |
Problem Statement: DMCplus Composite Documentation | Solution: Read / Printout attached PDF user's guide
KeyWords:
DMCplus, Composite, CLP, User's Guide, Documentation
Keywords: None
References: None |
Problem Statement: : Aspen Retail is forecasting diesel "loads" (deliveries) after the diesel runout point. | Solution: : First, check to see if the station has approval to receive "short" (substandard) loads. If the station is not approved for substandard loads turn on "short load" approval and reforecast the station. If the customer was approved for short loads then check to see if the customer has the "full diesel" flag turned one. If the customer does have the full diesel flag turned on turn this flag off and reforecast the account. If neither of these flags changes the expected forecast then go to the "Utilities" heading on the main Aspen Retail screen. Print out the report called "Transport Compartment Configuration Report". This report will easily show us the compartment configurations for all the trucks inside the terminal. Review the compartment configurations to insure that both "short" diesel configuration and double bulkheads are present on the terminals transports.
KeyWords: Replinshment Planner, Diesel
Keywords: None
References: None |
Problem Statement: What is Forecast delay? | Solution: The Forecast Delay is used to delay the forecast of stations that have not entered both a sales and inventory record. The forecast delay is a time (i.e. 9AM) that the system waits until before forecasting a station that has entered only ony piece of the sales and inventory information.
For example:
A station owner usually reports a midnight inventory reading , but does not enter the sales for the day because his sales cycle still has 6 hours left (6am-6am) . In order for this station not to be forecasted using book sales because actual sales have not been entered, the forecast delay time should be set for after 6am. At that point (6am) the station will be forcasted with whatever information it has even if there is only one peice of the information in the system.
KeyWords
Forecast delay
Keywords: None
References: None |
Problem Statement: Does Aspen SCM use TCP/IP to communicate? | Solution: Yes, Aspen SCM uses TCP/IP as a communication protocol.
Keywords: None
References: None |
Problem Statement: Is there a MIMI command which can be used within MIMI rules or macros, that duplicates the actions from the "Consuming Batches" and "Feeding Batches" options of the "Options" menu for the Planning Board ? | Solution: The "Consuming Batches" and "Feeding Batches" can not be issued through MIMI commands in current versions. However, the command S TRACE ROUTING [ind], is the new option that has been added into MIMI 7.02. With this, the user can run "option/routing" programmatically.
MIMI 7.02 should be available in January 2003.
Keywords: None
References: None |
Problem Statement: MIMI bar graphs and message bars not refreshing properly under Windows XP. | Solution: Under certain circumstances, MIMI application that were running correctly under Windows 2000 may behave differently when installed on Windows XP.
In Windows XP, if a MIMI command is running and generates a bar graph or message bar, the MIMI application will "freeze" if user puts any other window into focus. As a result, bar graphs and message bars will not be refreshed.
MIMI will only "unfreeze" after the command processing is completed.
Under Windows 2000 however, graphs and message bars will continue refreshing no matter what window is in focus.
To avoid this problem, the best solution is to modify the compatibility mode of MIMI executable to Windows 2000.
Like every other application running under Windows XP, the compatibility mode can also be changed for MIMI executable.
Open Windows Explorer and search for mimi.exe file. It should be located under program file/aspentech/aspenmimi/bin (FIG 1).
FIG 1
Right click on the executable and click on the Properties (FIG 2).
FIG 2
Select the third tab named Compatibility.
In the Compatibility Mode window, select the option Run this program in compatibility mode for and select Windows 2000 from the list box. Click OK button (FIG 3).
FIG 3
The MIMI application is now running under Windows 2000 mode and the above described problem will not occur anymore.
KeyWords
COMPATIBILITY MODE
WINDOWS 2000
WINDOWS XP
Keywords: None
References: None |
Problem Statement: I want to check in my case for any instances where I have a letter "B" followed by a variable name which includes the "?" character, in any Expert System rule. It seems that if my search string is "B?", it treats the "?" as a wildcard representing any value, so the search returns all instances of the letter "B". Is there any way to search for the literal string, "B?", in my case? | Solution: The GUI Search function is accessed via the menus, Data | Search..., and uses the question mark character "?" as a wildcard. Searching for character strings containing "?", such as the names of variables in Expert System rules, will actually return all instances of the search string, as if the "?" is any character.
To correctly search for and find strings containing a literal "?", you need to use the SEARCH command at the MIMI command line. For example, to search for the literal string "B?", the command would be as follows:
SEARCH "B?" * INFO
where the results of the search would be placed in the INFO table.
KeyWords
search
expert system variables
"?" wildcard
Keywords: None
References: None |
Problem Statement: The MIMI case crashes when trying to search for any string. The search fails with the error "Cannot delete the $SEARCH set" and MIMI crashes. | Solution: This problem occurs when the $SEARCH set is used either as a Before or After macro.
Use the following workaround to correct the problem: Remove $SEARCH as the Before or After macro.
KeyWords
SEARCH
$SEARCH
Keywords: None
References: None |
Problem Statement: When using the NUMERIC function in my Expert System rules to determine whether a string is a numeric or not, the function evaluated to True when checking strings such as 1D0 and 1E0. These strings should have evaluated to False using the NUMERIC function. | Solution: Values such as #D# and #E#, where # represents any valid numeric digit, could be considered as numeric values (double precision and scientific/exponential notation, respectively), thus the NUMERIC function is working correctly.
If the strings #D# and #E# are actually used as character strings by the end user, the MIMI programmer needs to write a more complicated rule to parse the string for these character sequences, rather than simply using the NUMERIC function to check.
KeyWords
NUMERIC
NUMERIC function
string evaluation
Keywords: None
References: None |
Problem Statement: You have to run your MIMI LP model with different MIMI versions in different sites of your company. You are using the CPLEX optimizer. Why can it happen that you see different results when running the exact same case (same MIMI model, same CPLEX parameters)? | Solution: Check the attached three CPLEX log files obtained running the same model respectively with CPLEX versions 6.0 (MIMI > v5.x), 7.0 (MIMI v6.2, v7.0, v7.1) and 8.1 (MIMI v7.2). As you can see, CPLEX finds an optimal MIP solution for versions 6.0 and 8.1, although with different values for the objective function, while it runs out of time in version 7.0. What has changed in the three versions that is causing this behavior?
Parameter MIPEMPHASIS explains what you are seeing. If you search "MIP emphasis:" in logs 8.1 and 7.0, you will see that their defaults changed in these two versions. 6.0 does not have this control at all. This is just one example that, even if users are using the same controls in a case, CPLEX internal defaults may change among different versions.
In particular, MIPEMPHASIS in CPLEX 7.0 by default emphasizes optimality. This setting will decide how to travel through the MIP tree to get the better solutions. It really affects how many integer solutions are found and how good the solutions' quality can be. When turned out, fewer integer solutions are found and, after about 600 seconds, the solution is still not any better comparing to what CPLEX 8.1 can find in 146 seconds because MIPEMPHASIS in 8.1 is set to "balance optimality and feasibility".
CCPLEX Table - MIP Emphasis Indicator (MIPEMPHASIS)
Possible Values:
0: Seek a balance between searching for feasible solutions and proving optimality
(CPLEX 8.1 Default)
1: Emphasize feasibility over optimality
2: Emphasize optimality over feasibility
(CPLEX 7.0 Default)
3: Emphasize moving the Best Bound
KeyWords
MIPEMPHASIS
CPLEX
CCPLEX
Keywords: None
References: None |
Problem Statement: Translation of MIMI Help Files into other languages | Solution: Previous solutions already describe the method to change the language of MIMI Application (Batch Files) and how to convert the MIMI Help files (Service Packs) for MIMI 5.0 and 5.1. Please, click on the link provided to access these solutions.
However, it has to be noticed that although the MIMI application is fully converted into the desired language by using the batch files, the MIMI Help files will be partially converted with the Service Packs. Please note that with MIMI 6.0 (available mid-July), these Service Packs will be included in MIMI Application.
The Service Packs that are use to convert the MIMI Help files into another language will translate only two manuals: the Aspen MIMI
Keywords: None
References: Guide and Navigating Aspen MIMI.
This is because the above mentioned modules contain a great amount of information that is user oriented and should be sufficient for an overall understanding of MIMI product. The remaining modules are consultants oriented. |
Problem Statement: Aspen SQLplus reporting에서 section type를 추가할때 아래와 같은 오류 발생 | Solution: Section type를 사용하기 위하여 마지막에는 반드시 SELECT 를 사용하여 Table 에서 값을 읽어와야 합니다.
예: 아래의 Procedure Proc는 계산을 하고 결과를 내보냅니다.
PROCEDURE Proc
LOCAL T REAL;
LOCAL B REAL;
LOCAL PCT REAL;
FOR (SELECT DISTINCT(IP_Plant_Area) AS area FROM IP_AnalogDef) DO
T = (SELECT COUNT(*) FROM IP_AnalogDef);
B = (SELECT COUNT(*) FROM IP_AnalogDef WHERE IP_Plant_Area = area);
PCT = (B/T)*100;
WRITE 'TOTAL: ' || T;
WRITE 'Count: ' || B;
WRITE 'PCT: ' || PCT;
END;
END;
위와 같은 스크립트로 프로그램을 짜면 본문에서의 오류가 발생합니다.
Temporary Table 를 사용하여 문제를 해결할 수 있습니다. 수정후 내용은 아래와 같습니다.
PROCEDURE Proc
LOCAL T REAL;
LOCAL B REAL;
LOCAL PCT REAL;
DECLARE LOCAL TEMPORARY TABLE MODULE.X
(TOTAL INT, Count REAL, PCT REAL);
FOR (SELECT DISTINCT(IP_Plant_Area) AS area FROM IP_AnalogDef) DO
T = (SELECT COUNT(*) FROM IP_AnalogDef);
B = (SELECT COUNT(*) FROM IP_AnalogDef WHERE IP_Plant_Area = area);
PCT = (B/T)*100;
INSERT INTO MODULE.X (TOTAL, Count, PCT) VALUES (T, B, PCT);
END;
SELECT * FROM MODULE.X;
END;
Keywords: Cannot find table 0
SQLplus Reporting
SQL Procedure
An unhandled exception occurred
KR-
References: None |
Problem Statement: My cases are getting too large. How do I reduce the size of the case? | Solution: This problem could be due to inefficient use of data storage blocks on the hard drive. Generally, if a user has a set or table that takes up 20 Kb, the operating system sees a data set of that size and stores it into a preset block size, 32 Kb or 64 Kb, depending on whether the operating system is using FAT16, FAT32 or NTFS. Now if the user starts creating another item, be it a set or table, the operating system sees it as a new data set and consequently, stores it into a new block of 32 Kb, or 64 Kb. As you can see, there is now wasted space in the data blocks. By compressing the case (CMPRCASE command or CAS2DAT/DAT2CAS), the operating systems see it as one contiguous data set and fills a block before using another, thereby eliminating wasted space, and consequently, shrinking the case size.
For more information on CMPRCASE, see the MIMI Help Files.
KeyWords:
Keywords: None
References: None |
Problem Statement: After saving an independent MIMI case, the case becomes dependent. Why? | Solution: Using the SAVE command will create a dependent case. The sets and tables are saved in the independent case or somewhere else, but the SSAVE saves the changes to the dependent case. Generally, this happens when users tries to create a side case and uses SAVE instead of the SSAVE command. To avoid this:
Open an independent case
Use the SSAVE <filename> (The case will remain independent.)
KeyWords
SAVE
SSAVE
SAVE AS
DEPENDENT
INDEPENDENT
Keywords: None
References: None |
Problem Statement: How to make sure batch files will continue to work after MIMI 7.x ? How to run MIMI.exe and MIMIAS.exe on the DOS Windows ? | Solution: To run either mimi.exe or mimias.exe from a DOS window prompt, whatever the current path is, use the START command.
START is a Windows command-line command that starts a separate window to run a specified program or command.
For example:
Typing start mimi.exe will open the MIMI GUI
Typing start mimias.exe will start the MIMI Application Server MIMIAS in a separate DOS window
However, the START command is not needed when using the full path for MIMIAS. For example, the following batch script will work, even if mimias.exe is launched without the START command. This command line (with the full path) will also work if typed directly on a DOS prompt.
"C:\Program Files\AspenTech\AspenMIMI\Bin\mimias.exe" -c"C:\Program Files\AspenTech\AspenMIMI\Cases\FcBatch.cas" -b > BATCH.log
Details:
Beginning MIMI 7.x, the START command is needed to run MIMI.exe and MIMIAS.exe. MIMIAS will work with the full command because all the DLL's needed are in the MIMI installation bin directory. mimi.exe does not so it needs the START command to find the DLL's that are not on the system path.
KeyWords
START
BATCH
SCRIPT
Keywords: None
References: None |
Problem Statement: Command SYS EXCELMIMI &PROCNAME {setname|tablename} does not work and you get a runtime error like "Runtime error 429 - can't create object". It is known that EXCELMIMI.EXE, the utility that can be used to export Mimi sets and tables to an Excel spreadsheet, gives an error when used with Excel from Office 2000. | Solution: Please find attached to this solution the patch that solves the problem. To install simply unzip the EXCELMIMI.EXE file and replace the old one located in the Bin subfolder of your Mimi installation folder, typically under \Program Files\AspenTech\AspenMIMI\Bin.
Other things you have to know if you are using command SYS EXCELMIMI:
When installing Mimi, choose the "Server Install" button
Again at installation be sure you select the AspenMIMI subcomponent called MimiX (press button "Select Subcomponents")
The "Chesapeake Distributed MIMI Request Broker" service must be up and running (check Services from Control Panel or task brk_serv.exe in the task list)
The Mimi case must have isolation off (to be sure execute command ISOLATION OFF either from the command line or a macro before running SYS EXCELMIMI)
KeyWords
MIMI-X
EXCELMIMI
SYS
Runtime errors
Keywords: None
References: None |
Problem Statement: Can not get access to the services when attempting to use the GET SERVICES MIMI command.
Under certain circumstances, users cannot access the services when launching GET SERVICES (command line or macro). The error message generated is "CANNOT GET SERVICES (STATUS = MIMI_RPC_ERROR)." In addition to that, another error message is generated when attempting to use the PROCNAME command: "PROCESS NAME HAS NOT BEEN DEFINED." | Solution: This problem is usually due to the Chesapeake Distributed MIMI Request Broker service is not started or the Broker installation is corrupted. Tech Tips # 106043 and 112802 in the Support Knowledge Base provide the necessary information to set up this service.
There is however another cause to this problem. Sometimes, if the MIMI installation has been completed with a firewall activated, it will prevent communication to the broker. This leads to the problem as described above. In order to resolve it, the user has to un-install MIMI, de-activate the firewall and re-install MIMI.
KeyWords
PROCNAME
GET SERVICES
BROKER
FIRE WALL
Keywords: None
References: None |
Problem Statement: MIMI 6.x does not work when the operating system's calendar is moved back in time. | Solution: This is a proper function of MIMI 6.x and is designed in this manner so that a licence file with an expiration date cannot be extended. If the calendar is moved back, MIMI will not function. Consequently, if the clock is moved back to the correct date, MIMI will function properly.
Keywords: None
References: None |
Problem Statement: How do I get the Library Version number to update in the Library Manager dialog box? I have changed the version number of the Library Case in LIBSYS and LMSYSLN, then re-installed the library, but the version number does not update. I was able to get the feature versions to update, but not the library version number. | Solution: The user should do a "formal" library upgrade by using the Add/Upgrade feature on the Library Manager GUI. The full path and filename (including the .cas extension) should be entered in the Add/Upgrade section, and then click "Add".
Library Manager will pick this up as an upgrade and update the currently installed features from this library as well. The user does not need to then go in and re-install from the Linked Libraries and Available Features list.
KeyWords
Library Manager
library upgrade
Keywords: None
References: None |
Problem Statement: I am having problems making MIMI Light Client run batch mode processing? | Solution: The MIMI Light Client does not support batch mode processing.
KeyWords
Keywords: None
References: None |
Problem Statement: When I try to run the broker in NT through Control Panel / Services / select the Chesapeake Distributed MIMI Request Broker and Start. The Service Control Dialog hangs up and crashes the system. | Solution: This symptom suggests that your broker is not installed correctly. Make sure your broker is stopped and then reinstall MIMI. NOTE: You should ALWAYS run the uninstall program before trying to reinstall MIMI.
KeyWords
Keywords: None
References: None |
Problem Statement: How to improve the performance of MIMI to resolve rules faster? | Solution: When MIMI/E needs to resolve a predicate, it must find the predicate in set $PRED. This is a linear search of the set, and it is not resolved at link time; it is done every time a predicate is fired. A linear search means that it starts at the top of $PRED and walks down the set in sequential order. Therefore, if $PRED has a thousand entries, it will take an average of five hundred tries to resolve a predicate.
The consequence of this behavior is demonstrated in the following example rules:
RTEST
IF MARK TIME
AND RTEST1
AND MARK DURATION
THEN RTEST
RTEST1
IF MODIFY CHOSEN MAXCOUNT = 10000
AND MODIFY CHOSEN CODE = 8
AND CHOSEN = 10000
AND ?X IN CHOSEN
AND RTEST_CALL_RULE_1
THEN RTEST1
RTEST2
IF TRUE
THEN RTEST_CALL_RULE_1
In the example, the rule RTEST was added and
COLLECT
LINK
Now predicate RTEST and RTEST1 are in position 907 and 908 respectively in $PRED.
>RTEST took 32 seconds to run.
Next,
POSITION RTEST AT TOP
COLLECT
LINK
Now predicate RTEST and RTEST1 are in position 1 and 2 respectively in $PRED. The same >RTEST now only took 3 seconds to run!!!
The tip is: If a rule/predicate needs to be fast, put those entries higher in the SCAT. For rules that are not CPU intensive or rules that run in batch, put them last. Note, the order of set RULES, which is a list of all the rule sets, is determined by COLLECT. The order of $PRED is determined by LINK based on the entries in set RULES.
For CPU-intensive predicates, do not break-up into sub-predicates; rather contain the rule in one predicate if possible. You are sacrificing modular code, flexibility and maintenance, but you are buying performance. Therefore, do this judicially.
KeyWords
MIMI performance
Rules
rule resolution
Erules
Keywords: None
References: None |
Problem Statement: To select the data I require, I must use the SELECT command multiple times. Is there a better way to do this? | Solution: In many cases, CHOOSE is preferable over SELECT because:
CHOOSE is more flexible and provides greater functionality than SELECT.
CHOOSE is more powerful; By executing CHOOSE once, you can select data to level of precision that would take several iterations of SELECT command.
CHOOSE is faster than performing multiple SELECT statements.
CHOOSE's syntax follows standard SQL conventions, which many users already know.
CHOOSE differs from SELECT in that it requires a query, which you define in control set. CHOOSE selects set and table data based on the query you write. Before you can execute CHOOSE command, you must create a query in MIMI set that specifies the data you want to select. You can have more than one query in the same MIMI set.
Some benefits of using CHOOSE queries:
User may send CHOOSE output to user-specified set or table destinations.
Queries may have multiple criteria selection with logical "AND" and "OR" evaluation capability.
Ability to have symbolic substitution so that a library of common queries may be referenced.
Ability to query via logical hierarchies. For example, even though loop is over PRO set, query may reference tables dimensioned by FAM. This is accomplished by virtue that FAM is related to PRO via PROTYPE.
A query must be created in a MIMI set before executing CHOOSE.
To create a CHOOSE query:
Type the query keywords in the set's Code.
Type the corresponding query clause in the set's Description.
Query set contents:
Each query consists of the query name followed by keywords.
Some keywords are required, and others are optional.
Each keyword in Code has a corresponding clause in Description.
See the MIMI online help for a full description of the CHOOSE command's query keywords and clauses.
KeyWords
CHOOSE
SELECT
query
Keywords: None
References: None |
Problem Statement: MIMI/E LINK and rule calling efficiency | Solution: Rules are linked prior to execution. MIMI/E performs the link step during the LINK command or when a >rulename statement is encountered. Thus, a macro calling several rules in succession (figure A) is less efficient (higher execution time) than a macro where the rules are fired by a single rule without the > sign (figure B). In rule RULEALL we assume that the predicate of rule RULE1 is RULE1, etc.
Figure A - Less efficient
Figure B - More efficient
Note that the automatic link step can be avoided by setting CNTLE(LINK,1) equal to NO. However, in that case the user must remember to run the LINK command if rules are changed.
KeyWords
MIMI/E
RULES
LINK
RULE CALLING EFFICIENCY
Keywords: None
References: None |
Problem Statement: Problem installing Sequelink Server 4.5.1 with linking option on AIX 4.3 platform | Solution: This problem occurs when there are no C compilers installed on the UNIX machine. The most logical solution is to install the 'cc' compiler, but that won't work. The 'oraxlc' shell script requires the 'xlc' compiler. As soon as 'xlc' compiler is present, the SequeLink Server installation should complete successfully.
Keywords: None
References: None |
Problem Statement: Can MIMI have a single instance of a license key with multiple copies of the application? | Solution: In th ALM version, MIMI would have a single instance of a license key on a centralized server with multiple copies of the application. MIMI Classic on the other hand needs a license code at install so there is a license key for every machine MIMI is installed on.
KeyWords:
Keywords: None
References: None |
Problem Statement: Is there a list of characters that should not be used in a MIMI set code? | Solution: Unexpected behavior has been observed when some special characters are used in the code portion of key MIMI sets. It is recommended that customers avoid the following characters in the code portion of MIMI sets:
( ) & $ % + - * \ / ? : > < ! # &
Other characters that could potentially cause problems include:
null (ascii=0)
newline (ascii=10)
Basically, any character that could be interpreted as a format symbol for C language's I/O functions should be avoided.
KeyWords
SET
SETS
CODE
DESCRIPTION
INVALID CHARACTERS
Keywords: None
References: None |
Problem Statement: Dialog font is not specified correctly for Japanese characters running on WIN NT 4.0 | Solution: Reselect the font in the properties window. This will rebuild the string. For example, use the Japanese font called FixedSys, which doesn't go through this aliasing system and the problem disappears on Windows NT 4.O. Another workaround is to avoid using Windows NT 4.0 if possible.
Detail Explanation:
The problem is in Microsoft Windows NT 4.0 somehow produces an alias for Japanese font names. So for example, the real name of the font file is msmincho.ttc but when it's installed, it displays a different name in Japanese. MIMI picks up the Japanese alias name.
Furthermore, if you look at the MIMI dialog windows, you will see on line 4, a "FONT" line, as follows:
Windows2000: -13,0,0,0,400,0,0,0,0,3,2,1,49,fontname
WindowsNT: -13,0,0,0,400,0,0,0,128,3,2,1,49,fontname
Each of these numbers identify a property of the font. Note the value 128 for WinNT where there is a value of 0 for 2000. Windows NT and 2000 are not compatible in this sense, that they build up these serial strings differently (the API is actually different).
Therefore, building a dialog with Japanese font on Windows 2000 and running it on Windows NT will not work unless the correct font is used.
KeyWords:
Keywords: None
References: None |
Problem Statement: Moved the ALM server to a different location and now the MIMI license key won't work. | Solution: To fix this problem, the installation needs to be redirected to the new ALM server.
1. Click on Start | Programs | AspenTech | Common Utilities | FlexLM License Management Selector.
2. Click on the first radio button which reads "Point to Aspen License Server to get a license."
3. Just below, type in the name of the new ALM server.
4. Click OK.
5. Try starting MIMI again and it should recognize the new ALM server.
If the problem persists, please contact the helpdesk for additional assistance.
KeyWords
MIMI
LICENSE MANAGER
LICENSE KEY
Keywords: None
References: None |
Problem Statement: Under certain circumstances, the BILIND table is not being cleared properly by MIMI | Solution: Under certain circumstances (i.e. when activities are deleted from the schedule), the BILIND table is not being cleared properly by MIMI. That is what a customer recently faced with his model. If this is the case, the user must verify that the entry UBI (Use BILIND as BOM) has been added to the table CMAN. He will also have to set CMAN(UBI) to YES. By default, parameter UBI is set to NO.
Additional information can be found in MIMI Online Help, index BILIND.
Keywords: None
References: None |
Problem Statement: Getting WinRPC error messages when running mimixobjects_sample1.xls in the MIMI Application Client. | Solution: There are two ways of resolving this issue:
Method 1
Stop the broker and then Search for the following files in your \winnt\system32 directory and remove them:
lm.dll
mrcapi.dll
atlm2.dll
errmod.dll
Then re-boot the PC and make sure the broker is running. Also make sure environment "path" contains the path to the "c:\MIMI\bin" directory. Of course the "c:\MIMI\bin" directory will be different if he installed in a different location.
If the above method does not work, perform a Find in the entire hard drive and if you find another copy of those dlls mentioned, delete them and re-boot. WARNING: You should have only one copy of these dlls on your PC.
If method 1 resolves the problem, it means that the problem is specific to this one installation and the user had residues from previous installations that conflicted with the new MIMI installation.
Method 2
If method 1 fails, then the MIMI installation needs to be modified to its original state.
Copy the specified 4 dlls from \MIMI\bin directory to \winnt\system32 directory
Reboot and try again
KeyWords:
Keywords: None
References: None |
Problem Statement: I get an intermittent MIMI broker error message stating "Broker failed to start." | Solution: This is caused by the broker service attempting to start before the ALM services starts. Since the MIMI broker is a MIMI executable running as a service, it needs to get a licence from the ALM server. But if the broker starts before the ALM service starts, obtaining a licence from the ALM server is impossible and the broker cannot start.
The workaround is to set the broker to manually start and make sure the user has the rights to start a service on the MIMI workstation. This way, the ALM server service is guaranteed to start before the MIMI broker service and the MIMI broker can lease a licence from the ALM server.
Keywords: None
References: None |
Problem Statement: When MIMI starts in UNIX, you get the following error: "Error opening message file." | Solution: Confirm that the MIMIHOME environment variable is to the correct path. It should be the directory where MIMI is installed, for example, /MIMI. If MIMIHOME is set correctly, then the MIMITEXT.DATA file may be missing. (This is the file that contains all of your error messages.) Search for the file in your $MIMIHOME/bin directory. If it is missing, then you must request this file from customer support ([email protected]). Be sure to include the version of MIMI you are running when submitting the request.
KeyWords:
Keywords: None
References: None |
Problem Statement: Increasing the maxcount of a set results in "Case corrupted, not enough memory - reload case file." | Solution: A customer recently tried to increase the MAXCOUNT of a set to 100000 and received in the message bar the following error message: "Case corrupted, not enough memory - reload case file".
This message occurs when MIMI can not allocate enough memory to hold the existing set as well as the new set it is trying to build.
Here are different things that can help to solve the issue:
Prior to increasingReduce the MAXCOUNT of the sets to the actual count. If the set is empty, reduce the MAXCOUNT to 1.
Compress the case (CMPRCASE) to remove any wasted space.
If the above steps are not sufficient:
Load the case file again and make some of the large sets/tables transient and perform a page out (see MIMI Online manual for syntax) .
It has to be noticed that when MIMI is not able to allocate memory , it does an automatically page out. Which sets and tables are paged out depends on the switch 12 option (OPTION/CONTROL switch - Find more about the switches in MIMI Online Help).
Also if you make frequently used of sets/tables transient and they are paged out often then the user can experience severe performance problems. An interesting MIMI command called PSTATS displays a report in the INFO table that lists the most frequently used transient sets and tables.
Keywords: None
References: None |
Problem Statement: Aspen SCM crashes immediately at startup, either when you try to open a case file, or when you simply open Aspen SCM from the Windows Start menu. | Solution: The cause of the crash may be that the FLEXlm License Management Selector utility is not correctly configured.
You run this utility from the Windows Start menu:
Start | Programs | AspenTech | Common Utilities | FLEXlm License Management Selector
Examples of incorrect configuration can be:
- You are pointing to an inexistent license file (Option 2-License File or Option 4-Combined)
- You are pointing to an inexistent or incorrectly configured ALM server (Option 1-License Server or Option 4-Combined)
The solution to avoid this kind of crash is to double-check and correct this configuration.
If you have a server type license (i.e. that uses ALM), you select the Single Server (first option, radio-box Point to Aspen License Server to get a license) and enter the ALM server name (i.e. MYSERVERNAME, most probably your PC itself) inside the corresponding textbox. Optionally you can also enter the Port Id used by ALM (generally it is 27000).
If you have a client type license file called mylicensefile.lic located in folder C:\myfolder, then you select the License File (second option, radio-box Select Aspen License File to get a license) and enter the full name of your license file C:\myfolder\mylicensefile.lic in the corresponding textbox.
Note: This behavior has been corrected in Aspen SCM v. 7.2 and later, where - if the license is not found - you get an error message saying that the licensing information required to run MIMI is not available.
Keywords: DUMP
CRASH
LOADING CASE
MIMI
ALM
ASPEN LICENSE MANAGER
References: None |
Problem Statement: Can I open or close an Activity Editor or the Planning Board from within a rule or macro? Is there a way to define an after-procedure for an Activity Editor? | Solution: The MIMI command to be used is S MODIFY, which is effective when the Planning Board is visible. This command, depending on the argument you supply to it, can either display the Activity Editor, if not already visible, or close it removing it from view.
The syntax in the first case is:
S MODI[FY] ind
where:
ind: is an activity index.
The syntax in the second case is:
S MODI[FY] CANCEL
On the other hand, you cannot define an after-procedure, i.e. a rule or macro which is executed after closing the editor, for the Activity Editor.
You probably know already that to open the Planning Board from code you have to type MAIN. In addition to this you can also close the Planning Board from within your MIMI code, and the command to be used is: DESTROY MAIN1
The DESTROY command is used to close many types of MIMI windows.
KeyWords:
ACTIVITY EDITOR
PLANNING BOARD
S MODIFY
CANCEL
MAIN
DESTROY
Keywords: None
References: None |
Problem Statement: Why is $BATCH failing when it runs in batch mode but not if it is run from the command line?
$BATCH probably expects certain set indexes to be established. When you load a case interactively, $LOAD$ runs and sets these indexes. Three possibilities are LANGUAGE, SCRNRES, and RBTROLES. There could be others. | Solution: ? Add the administrative parts of $LOAD$ to the beginning of $BATCH.
- Include everything prior to "CAP specific functions" and "application specific functions".
1. The library manager section can be left out.
2. The special language translation section can be left out.
Also...
? You can test this situation by loading your case without running $LOAD$ by holding the CTRL key down when the case loads. Then run $BATCH.
- If it fails this way, then you know $LOAD$ is doing something $BATCH needs.
? Include batch logging [<MLMSG ] to an external file in $BATCH.
? Include error traps [ ON ERROR codelabel ] in $BATCH.
- Write an error message to the batch log.
- Set &EXIT in error traps so BAT or CMD files can detect the error with %ERRORLEVEL%.
Keywords: Batch mode
References: None |
Problem Statement: How do I take data from MIMI and place it into a text file? | Solution: There are two ways to do this:
If the data is not very large, you can cut the raw data and paste it into a text file. After that, you will have to modify the text file itself to a fixed length or a comma delimited file, depending on the preference of the user.
If the data is a large amount, you can use the write command to move data from a MIMI model to a specified external file, in this case, a text file. For use of this command, please reference the MIMI help files by going to the help file, choose the search tab, type in "WRITE" (all capital letters) at item 1, then select "implied write.". This will get you to the "moving data out of your MIMI model" section. Unfortunately, the details of this command are too extensive to document here.
KeyWords
Keywords: None
References: None |
Problem Statement: I have used underscores in the names of my MIMI dialog objects before without any problems. However, sometimes my dialogs do not appear, or just the title bar appears when I use underscores in object names. What is causing this and how can I fix it? | Solution: There is nothing wrong in using underscores for object names in MIMI dialogs, as long as you are careful not to use extensions on resources where it is not intended.
For example, the name "PB_APPLY" is okay because "PB" is not a resource type - "PUSHBUTTON" is. However, when you use "LABEL_SOMETHING" or "TEXTBOX_SOMETHINGELSE", you run into problems because LABEL and TEXTBOX are resource types. If you use the name, "PUSHBUTTON_APPLY", instead of "PB_APPLY", then you would also run into this problem.
Rules and macros can dynamically alter dialogs using extensions on resources (e.g. DATA_SETLST). If you accidentally use the extension on a resource type, it confuses MIMI and causes it to assign negative values in the height geometry, making the dialog to appear completely collapsed or not at all.
To avoid this situation, simply change object names, such as "LABEL_SOMETHINGS" to "LBL_SOMETHINGS", and "TEXTBOX_SOMETHINGELSES" to "TXTBOX_SOMETHINGELSES", or similar non-use of resource type names.
KeyWords:
MIMI
dialog box
dialog builder
object name
Keywords: None
References: None |
Problem Statement: SELECT (syntax for selecting set data) runs too slow in my MIMI rule. | Solution: If you have a rule containing SELECT statements and you think it is taking too much time to run (for example you can see that through the MARK TIME command), then you may want to check the MAXCOUNT of the CHOOSE set.
If it is unnecessarily big, then your SELECT will run at a considerably lower speed if you decrease the MAXCOUNT of CHOOSE.
For example, a customer had the rule RTEST below started by macro MTEST. That rule was exactly the same in two different case files, but in one case it was executing in more than one minute, in the second case in 1 second. In both cases the data and the definitions of the involved sets (CHOSEN3 and CHOSEN4 in the example below) were exactly the same.
Well, it turned out that the CHOOSE set in the case where RTEST was running extremely slow had a MAXCOUNT of 2,700,000. Changing that MAXCOUNT to a more reasonable number fixed the problem.
***** Macro starting the test rule
(MACRO MTEST
MARK TIME
>RTEST
MSG &DURATION
END
***** Test rule containing SELECT statements
RTEST
IF
TRUE
AND
:CNT = '0'
AND
WHILE ?I
AND
SELECT CHOSEN3(109T.0683.3.3.3,C)
AND
SELECT CHOSEN4(109T.0683.3.3.3,C)
AND
:CNT = :CNT + 1
AND
:CNT LE 100 OR BREAK ?I
THEN
RTEST
KeyWords
SELECT
CHOOSE
MARK TIME
PERFORMANCE
Keywords: None
References: None |
Problem Statement: MIMI splash screen won't disappear when loading MIMI 6.x and higher. | Solution: This problem is a result of using the COMBINED option in the FlexLM License Management Selector. To get around this, use one of the following 2 work arounds.
If you are using ALM:
Click on Start --> Programs --> AspenTech --> Common Utilities --> FlexLM License Management Selector.
Click on the first radio button for "Single Server" and fill in the name of the server where ALM is installed.
Click OK.
Try starting MIMI again.
If you are not using ALM:
Click on Start --> Programs --> AspenTech --> Common Utilities --> FlexLM License Management Selector.
Click on the second radio button for "License File" and browse to the license file (*.lic) on your PC.
Click OK.
Try starting MIMI again.
KeyWords
Keywords: None
References: None |
Problem Statement: Unable to open or create scratch file CMP 1216.scr when running CMPRCASE utility. | Solution: By default, the CMPRCASE utility writes out its scratch file to the c:\ drive even if the utility does not reside on that drive. In the case where users are locked out of the c:\ drive for security purposes, CMPRCASE will still try to create a scratch file on the c:\ drive.
It is possible to redirect the CMPRCASE scratch file (CMP 1216.scr) by following these steps:
Go to a DOS prompt.
Change directories to c:\program files\aspentech\aspenmimi\bin.
Type one of the following 2 commands:
cmprcase ..\cases\gtest.cas -nt:\mimi\gtest.scr --> [If the case resides in c:\program files\aspentech\aspenmimi\cases...]
OR
cmprcase t:\mimi\gtest.cas -nt:\mimi\gtest.scr --> [If the case resides in t:\mimi...]
Where...
gtest.cas is the name of your case
t:\mimi is the drive and directory where you want the scratch file to be redirected
KeyWords
CMPRCASE
scratch file
CMP 1216.scr
Keywords: None
References: None |
Problem Statement: Why do I get error message "CNTLINV contains wrong entries" ? | Solution: Under certain circumstances, error message "CNTLINV contains wrong entries" (see Fig 1) may pop up when attempting to invoke the Inventory Grid (Planning Board / Options / Inventory Grid).
FIG 1
To avoid this problem, please verify the two following items:
Do not use another set to display the list of the inventories. Only PRO set is recognized by the Control Inventory Grid set (CNTLINV).
If PRO set is Hashed format and the set is being modified, the hashed list is no longer valid. To make sure the set is re-hashed each time you modify it, do one of the following: Create an After Procedure for the set that executes the HASH command. Note: make sure the Chain Options attribute is set to Yes, so the After Procedure will execute if the set is modified by rules or macros. If a rule or macro is modifying the set, execute the HASH command in the rule or macro. The MIMI Online Help provides further information about hashed sets.
KeyWords
CNTLINV
INVENTORY GRID
HASH
PRO
SCHEDULING
Keywords: None
References: None |
Problem Statement: Why should you check the flag "Force installation of all core components" in MIMI installation? | Solution: All Aspen products install common third party tools as core components. This allows them to be shared among the products and tracked properly by the master installer. The idea of having check box "Force installation of all core components" in MIMI installation is to save installation time. For instance if a customer has many Aspen products all being installed on the machine, then a particular core component only has to be installed once by leaving that checkbox unchecked. The checkbox is there to force the installation of these core components bypassing the time saving logic of the master installer.
Sometimes these core components can get corrupted on the machine but the master installer does not know and thinks a component is already correctly installed, so does not install it again. How can the corruption happen in the first place? One way with MIMI is from having previous versions of MIMI on the machine, especially versions of MIMI installed with the Classic installation method (5.1 and prior). If you install a new version of MIMI, and then uninstall MIMI 5.x, this uninstallation will remove some common DLL's that the new version uses with core components. Now if you run the new version of MIMI it might not start. Also, when you reinstall the new version, the master installer thinks the core component is there so it does not install it again. The master installer looks in the AspenTech\Setup\uninstall directory for special ini files as part of its determination of installed products and core components.
So, checking the checkbox gives extra security that all the core components are on the machine. The only problem with checking the checkbox is that you might run into error message: "Installation of the component Noble Net failed - installation can not continue" (see below for an explanation of this error).
If you are installing on a new machine that never has had any Aspen products on it, then it will install all the core components anyway. If you uninstall MIMI and it was the only product on the machine, the uninstaller will ask if you want to uninstall the core components. If you do then the next time you install it should install all the core components anyway.
Error message: "Installation of the component Noble Net failed - installation can not continue". It can happen when reinstalling MIMI. Why? The MIMI Broker service depends on the Noble Net for portmapper service. If the MIMI Broker service does not shut down, then when the Noble Net Portmapper tries to reinstall, the existing service does not shut down, and that's right because the MIMI Broker service depends on it. Noble Net installation fails at this point. Restarting the installation fixes the problem because the MIMI service is now stopped so it does not interfere with the Noble Net service.
KeyWords:
FORCE INSTALLATION OF CORE COMPONENTS
CORE COMPONENTS
MIMI INSTALLATION
NOBLE NET
PORTMAPPER
PORT MAPPER
Keywords: None
References: None |
Problem Statement: How can a user have multiple languages selected and not face the Planning Board issue as described in Tech Tip 105030 ? | Solution: In a previous Tech Tip (105030), we described the problem of the multiple languages selection that causes the Planning Board to be empty after installing MIMI on Windows 2000 and how to resolve the problem by deselecting the languages from the Registry Settings or the Regional Options. However, users who indispensably need to have multiple languages selected can use this Tech Tip to resolve the problem. The workaround is to change the Planning Board Label Font to either TERMINAL or ROMAN.
Applying this workaround will allow users to select any language desired but will restrict the Planning Board view to only two fonts. AspenTech is currently working with Microsoft to resolve this issue.
Open MIMI application
Select OPTIONS --> SYSTEM from the menu bar.
Select the WINDOW ATTRIBUTES tab
From the PLANNING BOARD WINDOWS, click on the LABEL FONT button.
Select TERMINAL or ROMAN for the characters font.
You can adjust the FONT STYLE or SIZE of the characters if desired.
KeyWords
105030
PLANNING BOARD
FONT
TERMINAL
ROMAN
LABEL FONT
Keywords: None
References: None |
Problem Statement: Does MIMI add to Win.ini, System.ini, Autoexec.bat or Config.sys files? | Solution: MIMI does not add to Win.ini, System.ini, Autoexec.bat or Config.sys files. But it does install .DLL's to the WINNT\SYSTEM32 folder.
KeyWords:
Keywords: None
References: None |
Problem Statement: How to configure an ODBC driver to work with MS Access | Solution: The steps below are based on using Windows 2000 Professional. These steps may vary slightly depending on your operating system.
From the Start | Settings | Control Panel
Select Administrative Tool
Select Data Source (ODBC)
Click System DSN Tab then click Add tab
Select the correct ODBC driver (e.g. MS Access)
Data Source Name: DEFAULT (NOTE: Any name can be used for the Data Source Name.)
Description: ODBC for MS ACCESS
Click on the Select button and point to the location of the database.
Click OK to save the settings, then Click OK button again to exit out.
Test the MIMI model to see if the macro will import or export data.
Keywords: None
References: None |
Problem Statement: The cas2dat utility is hanging during the process. | Solution: To find out which set or table is causing the process to hang, perform the following steps:
From a DOS prompt, execute cas2dat until it hangs and then press Ctrl-C to break out of the process.
Open the *.dat file and scroll to the bottom of the file. The last set or table listed is usually what's causing cas2dat to hang.
Open the original case and locate the troublesome set or table.
What to look for in the set or table:
Set the maxcount to be equal to the actual count and save the case. Garbage data tends to linger at the end of sets and tables. By dropping the maxcount, it is an easy way to remove the bad data. Once the save is complete, you can set the maxcount back to its original setting.
Check the attributes by right clicking on the set or table. Make sure that the code and description fields are equal to or less than 64.
Once the problem has been found and corrected, save the case and re-run the cas2dat utility.
Key Words
CAS2DAT
DAT2CAS
Keywords: None
References: None |
Problem Statement: When I enter PROCNAME on the command line, I get the error message "PROCNAME has not been defined." | Solution: The problem is due to one of the causes described below. In most of the cases you need to re-install MIMI to solve it.
First of all you have to be sure that you chose the "Server Install" and not the "Standard Install" option when installing MIMI. Otherwise, you will not have Distributed MIMI functionalities, such as the PROCNAME command.
Check if the MIMI Request Broker service is up and running. If the broker is not started, start it manually. You can check its status either from the Services applet of the Control Panel, or from the Task Manager (the broker's task is called brk_serv.exe). In Windows 2000 you can see the services from the Start menu, "Settings" | "Control Panel" | "Administrative Tools" | "Services". Look for the service called "Chesapeake Distributed MIMI Request Broker", double click to access its properties. In the "General" tab, the Startup Type must be "Automatic". Press button "Start" to start the service.
If after checking, as described above, you see that the broker is actually running, then the PROCNAME problem is due to the fact that your broker installation has been "corrupted". The solution is re-installing MIMI. But what may be the cause of this corruption? Actually it is the DLL's and Windows registry keys used by the broker service that were corrupted. In the Windows systems it is easy that the right DLL's are overwritten with incompatible DLL's when installing other software. DLL files can even be corrupted when a program is using them. The registry and the services database also have the same problem. Moreover Distributed MIMI uses Winsock 1.2, TCP/IP and RPC drivers, and those drivers may be incompatible with some other software in the system. Not all setup programs (InstallShield) can avoid overwriting the good DLL's. Lots of installer wizards just force overwriting of all DLL's, without checking their versions. That makes things easier for them, but it can be a nightmare for other installers. Windows 2000 seems to be handling this problem better, but still not enough. Windows XP should manage these installation issues much better.
As said in point 1 above, the PROCNAME command is available only if you do a "Server" installation of MIMI. In addition, you should know that there is a system global variable called &PROCNAME, which contains the process name as returned by command PROCNAME. Such variable is always available, whatever type of installation you do. To see the contents of &PROCNAME, run "MSG &PROCNAME" from the command line.
KeyWords
PROCNAME COMMAND
MIMI REQUEST BROKER
BROKER
DISTRIBUTED MIMI
SERVICES
SERVER INSTALL
STANDARD INSTALL
&PROCNAME VARIABLE
Keywords: None
References: None |
Problem Statement: My company is moving to a Windows XP managed environment. Does AspenTech provide an msi file for the installation of MIMI in such an environment? | Solution: AspenTech does not currently support the msi format at this time. The msi format is the installation file format used by the Microsoft Windows Installer. AspenTech has a development project to eventually migrate all AspenTech installations to the msi format, but have not determined when or how long it will take to migrate the MIMI Family CD to the new installation system. AspenTech's Engineering Suite is the first group of products that will be migrating to the new format.
The current installation method for MIMI does install on Windows XP, but might not support features that are built into the Microsoft Windows Installer.
KeyWords:
MIMI
installation
Windows XP
msi file
Keywords: None
References: None |
Problem Statement: If MIMI doesn't start and returns a memory exception error from Windows, you may need to manually install the NobleNet Portmapper Utility. This condition is a chain reaction when the broker is not running because the NobleNet Portmapper is not installed properly.
Typically, this utility may need to be installed because:
The machine was not rebooted after the installation was complete.
The Portmapper may have already been installed on the machine prior to the MIMI install. | Solution: Before you begin this procedure, we assume that MIMI has already been installed and the MIMI Request Broker and the Noble Net Portmapper are not running.
Using Windows Explorer, browse to the "C:\Program Files\Common Files\AspenTech Shared\Portmapper" directory.
Execute the portint.exe program.
Select the "Install NobleNet Portmapper" and the "Start automatically during system startup" radio buttons.
Click the OK button.
If you get a successful message, click Yes to start the service. Click Cancel on the main screen to exit the program and go to step 9.
If you get an error such as "Failure: CreateService (The service already exists)", click OK and go to step 6.
Select the "Remove NobleNet Portmapper" radio button and the "Manual startup" radio button.
Click OK. You should get a message that the portmapper was successfully removed.
Go back to step 3 and select the "Install NobleNet Portmapper" radio button and click OK.
Once NobleNet is running as a service, you need to start the broker. Open the Windows Services screen and find the Broker service "Chesapeake Distributed MIMI Request Broker". Select the service so it is highlighted.
Click on the Startup button.
Select the automatic radio button and click OK.
Click the Start button.
KeyWords
NOBLE NET
NOBLENET
PORTMAPPER
BROKER
MEMORY EXCEPTION
Keywords: None
References: None |
Problem Statement: Receiving the error "Licensing to run MIMI is not available" when starting MIMI. | Solution: Go to Control Panel | System
Click on the Advanced tab and then the Environment Variables button.
Click on New button (below System variables) and enter the variable: FLEXLM_DIAGNOSTICS
On the next field, enter 1
Run MIMI again and it should generate a FlexLM error message about the system clock being set or changed.
Close all windows and run an Advanced Search for future files e.g. December 3, 2003 to December 3, 2004
Verify that there are files and folders set in the future.
Save the attached attribute changer utility to local machine and run it.
Do the search again to verify if there still files that is dated in the future.
Run MIMI application to test.
Once testing is complete, the environment variable should be removed.
IMPORTANT: This Environment variable not only is running diagnostic processes, it also can create log files in what ever the current directory of the machine is. If the current directory changes then a new log file can be created in that directory.
Removing the Environment variable at the end of testing is very important.
KeyWords
Installation
Keywords: None
References: None |
Problem Statement: You may want to have - in just one page - a comprehensive list of the sets and tables required for Aspen SCM Demand Management command DMDRP. Here is one that you may not have found in the official documentation. | Solution: DMDRP is a full featured Distribution Requirements Planning (DRP) calculator that processes the DEMI, DEMF, RECI, and RECF tables and performs the necessary DRP calculations to project replenishment orders at each warehouse and source.
It considers the lead time from one location to another, the reorder point, the minimum reorder quantity, the incremental reorder quantity, and the starting inventory at the warehouse. A "freeze" time can be specified so that new replenishment orders are only placed in the demand tables after the freeze time. DMDRP simulates the projected inventory level at each location and places an order to replenish when the inventory level reaches the reorder point. The quantity to be ordered is the minimum plus the number of increments required to maintain the inventory higher than the reorder point. Each planned replenishment is converted to two instances of demand: one entry in the RECI/RECF tables for the receiving location and an entry in the DEMI/DEMF tables for the shipping location. DMDRP is a recursive routine that will calculate the demand requirements for a multi-level distribution system. Thus demands generated on a warehouse because of an order from another warehouse will be considered as well in calculating the projected inventory position.
Data Requirements for DMDRP
The following information is required for DRP calculations. The names shown below in parentheses appear in DMDICT. They can point to a set/table of the same name or different name.
Original inventory by location (DMINV)
Incremental order quantity (DMOINC)
Minimum order quantity (DMOMIN)
Reorder point (DMOP)
Lead time for shipments from one location to another (DMLTIME)
Plant or source warehouse from which to restock each location (DMORDPOL)
Set of restock policies (DRPPOL)
Restock policy from DRPPOL set for each product (DMTYPE)
Index of restock policy from DRPPOL set for each product - usually built by an after macro on the DMTYPE table (DMPTYPI)
MJ related tables:
Cumulative days (TDAY)
Demand data (DEMI & DEMF)
Receipt data (RECI & RECF)
Pointer to first demand (DMDPT)
Pointer to first receipt (DMRPT)
DMCNTL entry:
Frozen number of days during which new replenishments are not accepted. (DRPFRZ parameter in DMCNTL)
Tables for DMDRP
Applications that require the DMDRP command make use of the following sets and tables [N.B.: The (warehouse set) can be DMLOC or a subset of DMLOC]
Name of Set/Table
Contents
Dimensions (for tables)
DMINV
Inventory by location
DMPRO x (warehouse set)
DMOP
Order point by location
DMPRO x (warehouse set)
DMOMIN
Minimum order quantity
DMPRO x (warehouse set)
DMOINC
Order increment
DMPRO x (warehouse set)
DMLTIME
Lead-time in days
(warehouse set) x (warehouse set)
DRPPOL
DRP reorder policies
Set
DMORDPOL
Source whse for restocks
DRPPOL x (warehouse set)
DMTYPE
Reorder policy by product
entries are from DRPPOL
DMPRO x 1
DMPTYPI
Reorder policy index by
product - index of DRPPOL
DMPRO x 1
TDAY
Cumulative days
TIM x 1
DEMI
Indexed demand data**
DEM x HDI
DEMF
Float demand data**
DEM x HDF
RECI
Indexed receipt data**
REC x HDI
RECF
Float receipt data**
REC x HDF
DMDPT
Pointer to first demand
DMPRO x 1
DMRPT
Pointer to first receipt
DMPRO x 1
Make sure that the header sets contain entries as described in the "Tables for Linking to MIMI Scheduling Models" section of the manual.
KeyWords
DMDRP
Keywords: None
References: None |
Problem Statement: How do I set up backup ALM 3.0 servers and the workstations to access them in case of failure of the primary ALM server? | Solution: Step 1: Install the secondary and tertiary ALM server on the desired servers and bring them online.
Step 2: Go to the MIMI workstations, click on Start | Programs | Aspentech | Common Utilities | and click on "FLEXlm License Management Selector." A window should now appear. On the 3rd quadrant of the window, enter the names of the Primary, Secondary, and Tertiary ALM servers. This MIMI workstation will now go to the alternate ALM servers if connection is lost between the ALM server and the workstation.
Keywords: None
References: None |
Problem Statement: I get the error message "unable to obtain license" when I start MIMI. | Solution: Potential causes for this error are:
This error message is indicative of MIMI unable to lease a license from the Aspen License Manager server. This usually happens when there are more MIMI users trying to use MIMI than there are licenses.
Also, this error can happen if a user downloads only one license for use on a local ALM server installation. This is due to the MIMI broker running (it also needs one license).
The solution in case 1 is to shut down any unused MIMI sessions, thereby returning MIMI licenses back to the ALM server pool. The solution in case 2 is to download more than one license seat per license module. The generally recommended amount is 5 seats per license module.
Keywords: None
References: None |
Problem Statement: "Error in I2C Function" while running CAS2DAT. | Solution: The I2C error can be caused by one of several reasons:
If you are trying to run a cas2dat on a file that is already in a DATA format, you will get this error.
If the version of cas2dat is too old or too new in comparison to the version of the case file.
If there is so much corrupt data in the case that the utility can't even interpret the case file.
If none of these causes seem likely, then continue reading. Solving this problem can be a little tricky. Here's some suggestions on where to start:
Run cas2dat and allow the utility to fail. If you look, you can see that the utility will start to create a data file. Data files are ASCII so they can be read with any text editor, like Notepad. So, open the DATA file and scroll all the way to the bottom to see what's making it crash. The last entry listed can tell you a lot about the problem. This will tell you that either that last entry (set/table) or the next consecutive entry in the catalog is causing the problem. This is where it becomes trial and error.
Look at the rowset and colset of the last entry and drop their maxcounts to be equal to the actual counts. This will delete any garbage (hidden) characters that are lingering at the end. Also, check for things like code and description widths beyond 64. After making these changes, save the case and run cas2dat again to see if it still fails. If it doesn't, you can reset the maxcounts when you reopen the new case.
If the cas2dat continue to fail, then you will need to find the next consecutive entry in the catalog. To do so, open the catalog and sort by "Catalog Index". Then, scroll down until you find the last entry from the failing cas2dat and see what entry is listed next. Begin to analyze this entry, just as you did in step #2. After making these changes, save the case and run cas2dat again to see if it still fails. If it doesn't, you can reset the maxcounts when you reopen the new case.
If none of these suggestions solve your I2C error, then you will need to send a copy of the case to [email protected] for further analysis.
KeyWords
I2C
CAS2DAT
DAT2CAS
Keywords: None
References: None |
Problem Statement: Is Aspen SCM supported on Windows XP SP2 ? | Solution: Aspen SCM has not been formally tested on Windows XP SP2 yet. AspenTech runs complete Aspen SCM testing on new platforms, but special considerations are generally not given for different Windows service packs.
From informal testing of Aspen SCM with Windows XP SP2, initial security alerts were experienced (maybe related to the firewall) which indicated that some features of the program had been blocked but had the option to unlock. After checking the unlock option, everything appears to work fine.
A brief status of official support of Aspen SCM on Windows XP SP2:
Aspen SCM is officially supported to run on Windows XP starting from version 7.0
Aspen SCM 2004 and below have not been officially tested on XP SP2
Aspen SCM 2004.1 (aspenOne 2004 update 1, planned release May 2005): no decision has been made yet regarding XP SP2 support
Aspen SCM 2004.2 (aspenOne 2004 update 2, planned release November 2005): all products should support XP SP2
You can check the attached solutions for additional questions regarding Aspentech products support on XP SP2.
KeyWords
WindowsXP
XP
SP2
Service Pack 2
Compatibility
Keywords: None
References: None |
Problem Statement: I am getting the error message "SOURCE1 set not found" when performing a set subtraction such as TMP = TMP - CHOSEN. Do you know what causes it? | Solution: Any command that modifies the size of a set or a table will create "holes" in memory. This means that while the memory used may be well within the range available, there may not be enough contiguous memory to create the table. This will result in the application running out of memory.
Saving and reloading the case can solve this problem. The SAVE and LOAD must be done before you run out of memory. Once out of memory, it may not work.
Also, upgrading the operating system to Windows 2000 Advanced Server and running a modified MIMI executable, what is called MIMI 3GB or "Big" MIMI, will let the application access up to about 2.8GB of memory. It is planned that the MIMI executable will be delivered in this format for future new releases. At the moment you have to ask for it from MIMI Support. In order to increase the virtual address space of Aspen MIMI 3GB (which otherwise would still be limited to 2GB) you have to add the /3GB switch in the boot.ini file. You can see below an example for the boot.ini file from a Win2000 Advanced Server machine.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server 3GB" /3GB /fastdetect
KeyWords
MIMI3G
SOURCE1 SET NOT FOUND
Keywords: None
References: None |
Problem Statement: What is the difference between the Application Client and Light Client? | Solution: Application Client: The MIMI case resides on a workstation or server. When the case is opened, all processing will be done on the workstation, utilizing the workstation CPU, memory, and other resources. Processing is dependent on the workstation hardware and processing power.
Light Client: The MIMI case resides on a server. When the case is opened, all processing is done on the server, utilizing server CPU, memory and other resources. Processing is dependent on server hardware, processing power, as well as number of users accessing server at the same time.
KeyWords:
Keywords: None
References: None |
Problem Statement: How can I solve the "brand new product" Demand Management problem in Aspen SCM? | Solution: DM provides 3 formulas for forecasting new products: GOMPERTZ, SPRING, and LOGIT. Each of these do not require any observations, but you have to provide parameters which govern their shape and their asymptotic value.
GOMPERTZ and LOGIT basically increase monotonically, with a possible point of inflection, until they reach their "saturation level", while SPRING allows for the possibility of overshooting the saturation level before reaching steady state. None of them are made to reflect long term seasonality or any other attributes of a product, but they are primarily concerned with the introduction period.
Another option of dealing with a brand new product: if you are doing a product replacement, sales for the new product are probably not based on marketing intelligence and history for the old one will be your best guideline. In this case your main concern won't probably be what the intro period will look like, but you just want the new product to take the place of the old one. Then you would be much better off by choosing a similar product and simulate forecast for the new product based on the old one.
Moreover, if you have some mathematical shapes in mind, you can also use the MULTI-REG method, by pre-loading the shapes into a table, and using that to forecast by.
KeyWords
Demand Management
Brand New Product
Forecasting Methods
Keywords: None
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.