Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Clipper Queries failing to run from the Batch Environment

Clipper Queries failing to run from the Batch Environment

Problem

I have followed the on-line help system and created a batch file that runs a clipper query.

All the parameters look correct, but I get a error executing the report displayed in the log file.

Example 1 Log File:

Cmd:  "D:\Program Files (x86)\Micro Focus\Modernization Workbench\Scripts\BRP\ClipperSearch.bj" "(20130225_0602)All Code_ClipperSearch_Possible Data Truncation.log" "Workspace=D:\Workspaces\HCOI_WS_EV.rwp" "Model=Cobol" "Project=All Code" "Criteria=General:Coding Standards\Move Statements\Possible Data Truncation" "ListName=Data truncation" "Category=General" "Accumulate=False" Job: D:\Program Files (x86)\Micro Focus\Modernization Workbench\Scripts\BRP\ClipperSearch.bj

18:02:05 >Open D:\Workspaces\HCOI_WS_EV.rwp          *WARNING* MWB is connected to the workspace 18:02:06 >Project All Code

18:02:06 Cuter .ClipperSearch (Prm.Criterion, Prm.Model, Prm.ListName, Prm.Category, Prm.Accumulate) 18:02:07  (failure) Model 'Cobol' not found in HCSearch.xml

 

Example 2 Log File:

Cmd:  "D:\Program Files (x86)\Micro Focus\Modernization Workbench\Scripts\BRP\ClipperSearch.bj" "(20130304_1233)All Code_ClipperSearch_Possible Data Truncation.log" "Workspace=D:\Workspaces\HCOI_WS_EV.rwp" "Model=COBOL" "Project=All Code" "Criterion=General:Coding Standards\Move Statements\Possible Data Truncation" "ListName=Data truncation" "Category=General" "Accumulate=False" Job: D:\Program Files (x86)\Micro Focus\Modernization Workbench\Scripts\BRP\ClipperSearch.bj

12:33:52 >Open D:\Workspaces\HCOI_WS_EV.rwp          *WARNING* MWB is connected to the workspace 12:33:54 >Project All Code 12:33:54 Cuter .ClipperSearch (Prm.Criterion, Prm.Model, Prm.ListName, Prm.Category, Prm.Accumulate) 12:33:54  (failure) Can not find criterion

 

Resolution

The parameters that are passed into the Brave bj files are case sensitive, so care must be taken when specifying the parameters. 

So the following parameters for the ClipperSearch.bj will not find the ‘Possible Data Truncation’ which is in the ‘General:Coding Standards\MOVE Statements’ area.

SET CR=Criterion=General:Coding Standards\Move Statements\

SET N=possible data truncation

SET LN=ListName=Data truncation

SET CT=Category=general

SET PRJ=Demonstration_COBOL

SET MODEL=Model=cobol

SET ADD=Accumulate=False

The parameters should read: 

SET CR=Criterion=General:Coding Standards\MOVE Statements\

SET N=Possible Data Truncation

SET LN=ListName=Data truncation

SET CT=Category=General

SET PRJ=Demonstration_COBOL

SET MODEL=Model=COBOL

SET ADD=Accumulate=False

The .bj scripts are text files that can be opened to check the parameters that are needed, to enable them to run.

It is possible to run one script that will populate a list, that is then used by a second script to produce a report.

If entities are re-registered (eg refreshed or verified), any entries they have placed within a list are deleted, as the entries may become invalid.

The running of ClipperSearch.bj can be included in a ‘Batch Refresh Process’ user-exit and should be used after the verification process has completed, such as the post verification user-exit.

 7571.Clipper_Queries.zip

# 2615515 & 2616692

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-03-14 09:51
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.