Rocket® Enterprise Suite

Can a job that is in the input queue or which is currently executing be killed from the command line in Enterprise Server JCL? Problem: How do you kill an Enterprise Server JCL job from the command line, even if the job is already in the input queue or currently executing? Resolution: A job that is in the input queue or which is currently executing may be killed by using the "CASOUT" command.   For example: casout -r<servername> -k<job#> casout -s<protocol:ip-addr:port> -k<job#> casout -l<servername> -k<job#> Our architecture's design is such that we first attempt a "soft kill" in which the process is notified that we would like it to go away.  If the batch initiator can terminate the job at that point in time then the JCL batch initiator terminates the user program, issues the appropriate S222 abend message and then the job terminates.    The JCL batch initiator process continue

After using the CASSUB command to submit a JCL job in Enterprise Server, how can this job be killed from the command line? Problem: After using the CASSUB command to submit a JCL Job in Enterprise Server, how can this job be killed from the command line? Resolution: To kill the job from the command line, use the CASOUT command and the /k<jobnumber> parameter. For example: CASOUT /rESDEMO /k4711 Detailed information about CASOUT can be found in Online Help. Old KB# 13970#netexpress#Server#EnterpriseServer#Enterprise#COBOL

This article address the inability to access JCL jobs after applying WrapPack (WebSync) for Net Express version 5. Problem: We have recently installed WrapPack (WebSync) for Net Express version 5 and are subsequently unable to access JCL jobs. After applying the WrapPack (WebSync) the product version was 5.2.0077. If you select a job that had been run before applying the WrapPack (WebSync) then you receive a "Job Not Found" error message. Resolution: Attached below is a utility that will resolve this problem. Save this in the directory where the "casspool.dat" file is. This will be the location that you can define in the JES section for the MTO Region. If you open up a Net Express command prompt you can navigate to that folder. Then you can then compile and run as follows in order to access the jobs: Cobol cassplfx.cbl dialect"mf" gnt; Run cassplfx Old KB# 13955#COBOL#EnterpriseServer#Server#netexpress#Enterprise

By default, MFDS runs on the well-known port 86. Is it possible to run MFDS on a different port? Problem: By default, Micro Focus Directory Server (MFDS) runs on the well-known port 86. Is it possible to run MFDS on a different port? Resolution: To specify a non-default port, the CCITCP2_PORT=[port value] environment variable needs to be set in the session before starting the MFDS process. For application clients that want to use a particular MFDS instance running on a non-standard port, the CCITCP2_PORT value also needs to be set. This technique allows altering the default port for a single MFDS instance, or running multiple MFDS instances on a single machine. There are various considerations to take into account when running multiple MFDS daemons simultaneously, such as port conflicts in Enterprise Server instances (ESDEMO uses fixed ports for some of its default listeners, and these will clash unless they are changed), and possible conflicts over file resources s

Animator freezes when querying a variable or hovering the mouse over a variable when using the Dynamic Debug feature in Enterprise Server. Problem: When querying a variable or hovering the mouse over a variable when using the Dynamic Debug feature in Enterprise Server, the Animator freezes. Why is this? Resolution: This may be caused by using a Net Express version prior to 5.0, and can easily be resolved by installing WrapPack version 5 or later. Old KB# 13962#EnterpriseServer#ServerExpress#Enterprise#Server#COBOL#netexpress

Unable to find console.log file under ESMTO or the Windows Search utility. Problem: I am unable to find the console.log file under ESMTO and the Windows Search utility cannot find the file either. Resolution: By default, ESMTO places the file in the C:\\Documents and Settings\\LocalService\\My Documents\\Micro Focus\\Net Express 5.0\\WORKAREA\\<ServerName> directory. To view this directory, go to Windows Explorer under the 'View tab and choose 'Tools/Folder Options' and then turn on 'Show Hidden Files and Folders'. If the 'Show Hidden Files and Folders' option is not set, the Windows Search function will not search through hidden folders and will not find the console.log file. Old KB# 13954#EnterpriseServer#COBOL#netexpress#Server#Enterprise

When upgrading from Enterprise Server 4.0 to 5.0, the CASXO0002s Switch Load Module for resource ORAP failed to load. Problem: When upgrading from Enterprise Server version 4.0 to 5.0, this message comes up: CASXO0002s Switch Load Module for resource ORAP failed to load 16:02:37 Module name ESORAXA.cbl. Resolution: When importing Enterprise Server regions from other servers, ensure that references to XA switch module locations are correct for the target machine. This issue was caused by importing to a machine whose product was installed into a different directory from the source machine. Old KB# 13958#EnterpriseServer#Server#Enterprise#COBOL#netexpress

Had installed Net Express 5.0 with WrapPack 5 and then removed it and went back to WrapPack 4 and then to WrapPack 3, but received the same error on all back levels. Problem: Had installed Net Express 5.0 with WrapPack 5 and then removed it and went back to WrapPack 4 and then to WrapPack 3, but received the same error on all back levels. Resolution: 1. Delete the log.html where the ESDEMO system directory is located. 2. Clear the journal by selecting "Journal" under "Display" on the left of Enterprise Server Admin page, then select delete at the bottom. 3. Start the ESDEMO by using userid SYSAD and password SYSAD for a different user. 4. In the case of a failure, go back to "Display", "Journal" and press "Export As Text" so that the journal.dat file gets converted to a .txt file for viewing. This is located in the "Repository Location" under the "Display", "Statistics" menu. 5. Send in the journal.txt, log.html and the console.log. Old KB# 13965#Enterp

Problem: SQLCODE -2000 SQLERRMC= unimplemented feature received when doing a fetch prior using Microsoft Access. Resolution: In orer to use scrollable cursors you need to specify EXEC SQL SET SCROLLOPTION STATIC END-EXEC after the CONNECT statement and make sure your ODBCRW32.dll is dated after June 1999. Old KB# 7068#netexpress#Enterprise#COBOL#MFDS#MainframeExpressandMFE#EnterpriseDeveloper

Problem: Poor performance in OpenESQL applications and SQL Assistant Resolution: Ensure that ODBC tracing is not enabled, else the performance will be severely impacted. OpenESQL tracing, enabled via either the SQL(TRACELEVEL=n) compiler directive, or the EXEC SQL SET TRACELEVEL n statement, may also impact performance of your application. Old KB# 7067#Enterprise#COBOL#MainframeExpressandMFE#MFDS#EnterpriseDeveloper#netexpress

Problem: Net Express 3.1 and 4.0 A Microsoft Access table has a MEMO field defined within it.  This is a large, varaible length text field.  When you try to insert or update data from OpenESQL you get a SQLCODE of -98. Resolution: At present, a host variable is limited to 64K in OpenESQL.  A MEMO field can go beyond this limit so with the current release of Net Express you cannot exceed 64K.  However, it is possible to use a MEMO field within this limit: 1) Define the MEMO host variable as SQL TYPE IS LONG-VARCHAR(64000). 2) Next, set the length of the host variable, move the data and initialize the null pointers.         move 64000 to host-variable-len.         move "test" to host-variable-val.         initialize host-variable-null.    this is required as the LONG-VARCHAR S

Problem: Need information on calling stored procedures that return data. Resolution: If nothing is specified in the call statement then INPUT is assumed. You can specify OUT or INOUT (for both input and output) ex. EXEC SQL CALL MFTEST (:host1 INOUT, :host2 out, :host3 ) END-EXEC Look in Bookshelf>Database Access> chapter 11 Stored Procedures. Old KB# 6860#netexpress#MainframeExpressandMFE#Enterprise#EnterpriseDeveloper#COBOL#MFDS

Problem: Is it possible to branch to or execute a procedure name defined in a lower level Resolution: Release: 3.1   It is not possible to branch-to-procedure or execute-procedure of a procedure in a lower level dialog. That is, it is not possible for a window or from the global dialog to branch to or execute a procudure in its push button. Although, the other way around is possible, i.e. you can branch to or execute a procedure in the global dialog or window from its push button. Attachments: T Old KB# 6862#Enterprise#MFDS#EnterpriseDeveloper#MainframeExpressandMFE#netexpress#COBOL

Problem: SQLCODE -19804 Illegal data Resolution: Some of the host variable definitions are most likely incorrect. You can use the OpenESQL Assistant to create a copybook containing appropriate host variables definitions for the columns you are working with. Refer to the Net Express Help for information on how to use the OpenESQL Assistant. Attachments: CC Issues.zip Old KB# 6812#MFDS#COBOL#Enterprise#MainframeExpressandMFE#EnterpriseDeveloper#netexpress

Problem: I want to use a MVS dataset name in the CICS FCT so I can identify the physical PC file. Can I do this in MFE CICS? Resolution: Yes. Go to the FCT Overrides tab. From there one can enter a MVS name that matches the PC physical file. Now you can toggle between the FCT's 'use catalog' tab and the CICS FCT without tying yourself to the Catalog, but you can still retain the identity of the physical file. Old KB# 6728#EnterpriseDeveloper#MFDS

Problem: An IBM assembler module is ending with S0C1 within the macro STIMER. Your program can be compiled and linked, because the IBM version of the macro has been added to your project. This macro sets the timer by means of the SVC 47, which is not implemented in MFE. Resolution: Usually the macro in used to put a program into a wait state. If the WAIT parameter is applied, you may as well omit the SVC 47 by commenting it out. A usage of STIMER may look like this:    ... DELAY  EQU   *                              STIMER WAIT,DINTVL=XK3MIN        ... XK3MIN  DS  0D                         8 bytes &nbsp

Problem: We have coded a DCB override for print records going to SYSOUT. It looks like this: REPORT    DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251) But on the OPEN of the dataset, we get a RTS139 error. What is wrong? Resolution: A COBOL program that writes output records may use a carriage control character or it may not. Since the JCL shows a record format of FBA and the supplied sample used a WRITE AFTER ADVANCING command, then you should use the NOADV compiler directive. It comes down to this: - a COBOL program uses WRITE AFTER ADVANCING for printing    - the program takes into account one byte carriage control character      for printing by adding an extra character ahead of the record to be written           This program should use NOADV    - a program does not add a one byte character to the front

Problem: I want to convert my data file from one character set to another (EBCDIC to ANSI), but I have packed fields which must not be converted. How can I do this in Mainframe Express (MFE)? Resolution:   First, one must make a .STR file so the Data File Convert function will know which fields to skip in its character set conversion processing.  Next, one can either use a .PRO file created from within the Data File Converter itself or by creating a new one via an ASCII text editor. And lastly, one can use this command in a MFE Command Prompt: run dfconv <.pro file> <input file> <output file> Old KB# 6722#EnterpriseDeveloper#MFDS

Problem: Using DB2 on the mainframe, it is possible to specify multiple databases under one subsystem - it is possible to have the same hierarchy within Mainframe Express SQL Option? Resolution: Yes. On the host, databases and storage groups are used to enhance performance by enabling data to be stored across multiple volumes. In Mainframe Express, there are no such considerations.  However, SQL Option does support storage groups and databases so the same DDL that is used to create the tables on the mainframe can be run in MFE.  If the user chooses not to specify a database for the table, the default database of DSNDB04 will be used. Old KB# 6725#MFDS#EnterpriseDeveloper

Problem: use dialect that is a mainframe dialect and try to call more then 8 character name like cbl_exe_run_unit Resolution: I used the Call identifier version instead of Call 'Literal" and the problem subsides. This is implied in the discussion in the doc about "MapName".  It said that Call Identifier was not truncated.   This worked: 004910     Display "Test NoTruncCallName for Charles". 005000     Move  "CBL_EXEC_RUN_UNIT" to CallName. 005010     call  CallName using  command-line 005100                   by value     command-line-len 005200                   by reference run-unit-id 005300 &nb

Problem: We are moving from HOD to PCOMM. How can we setup the IMS terminal emulation for this in Mainframe Express (MFE) v2.5? Resolution: There is an .INI file with comments and directions for MFIMS emulators located in mfe\\mfims\\source\\mfims.ini Also see Chapter 7, section named 'Telnet 3270 Terminal Emulator Interface' of the IMS Option Technical Guide. Old KB# 6726#EnterpriseDeveloper#MFDS

Problem: What is the scope of the analysis tool?  If I have workgroups with directories of source code, will they be brought into the option, or do I need a program compiled before it is analyzed. Resolution: Yes, one must compile programs before they are brought into the Analysis Option and unlike Test Coverage which is a BUILD setting and can be specified individually, the Analysis Option is a PROJECT setting and is set for the entire project. Old KB# 6719#MFDS#EnterpriseDeveloper

Problem: I am using Mainframe Express. Can I debug a user written preprocessor? Resolution: MFE Release 2.5 You need to debug as Non Mainframe - if you don't see the Non Mainframe tag, this needs to be turned on in Options>Debug, Enable debugging of Non-mainframe programs... The command line to use is:        COBOL yourprogname directitves.   Directives will need to include the PREPROCESSOR or P directive naming the user preprocessor. Also see the topic Writing a Preprocessor in the on line help for further information So your command line would look something like this:       cobol mypgm p(myprep parm1) endp;   Old KB# 6717#COBOL#ServerExpress#netexpress#MainframeExpressandMFE#MFDS#Enterprise#EnterpriseDeveloper

Problem: When trying to delete a host QSAM dataset, a customer reported that they were receiving a RACF error. The customer is able to delete the same dataset in TSO or from a FTP command prompt. Error message received was:    MFDAS01 the user profile is not defined to RACF There are three groups of users, two cannot delete files, and one group can. Resolution: This was  traced to a RACF problem.  Typing "AD ('mytsoid.*')" at a TSO ready prompt, gave the user a RACF profile. Once that was done, there was no problem deleting datasets from the mainframe via Drag & Drop. Old KB# 6751#EnterpriseDeveloper#MFDS

Problem: We have downloaded some host JCL and it uses a program named ICEMAN. Does Mainframe Express support this? Resolution: ICEMAN is IBMs older name for DFSORT (Data Facility Sort).  Make an Alias in Mainframe Express for it, via 'Project>Project Settings>Aliases tab' pointing to MFJSORT. Old KB# 6727#EnterpriseDeveloper#MFDS