Here is the COBOL code I wrote for subscribing to the event:    $set ilusing"DevExpress.XtraPrinting"    $set ilusing"DevExpress.XtraPrinting.Links"    $set ilusing"DevExpress.XtraPrintingLinks"                          .                          .                          .     method-id btnPrint_Click final private.       local-storage section.         01  link                                       type PrintableComponentLinkBase.         01  PrintingSystemBase        type PrintingSystemBase.         01  component                         type IPrintable.       procedure division using by value sender as object e as type System.EventArgs.           set component to gridControl1           set link to new type PrintableComponentLinkBase.           set PrintingSystemBase to new type PrintingSystemBase.           set Component to component.           ATTACH METHOD link__CreateReportHeaderArea to link::CreateReportHeaderArea       end method.

Here is the COBOL equivalent: $set ilusing"System" $set ilusing"System.IO" $set ilusing"System.Security.Permissions" class-id Watcher.Watcher. working-storage section. method-id Main public static. local-storage section. procedure division. invoke self::Run goback. end method. method-id #Run public static attribute PermissionSet(type SecurityAction::Demand, property Name="FullTrust"). local-storage section. 01 any-key pic x value spaces. procedure division. declare args as string occurs any = type System.Environment::GetCommandLineArgs * If a directory is not specified, exit program. if args::Length not = 2 * Display the proper way to call the program. display "Usage: Watcher.exe (directory)" goback end-if * Create a new FileSystemWatcher and set its properties. declare watcher as type FileSystemWatcher = new FileSystemWatcher set watcher::Path to args[1] * Watch for changes in LastAccess and LastWrite times, and * the renaming of files or directories. set watcher::NotifyFilter to type NotifyFilters::LastAccess b-or type NotifyFilters::LastWrite b-or type NotifyFilters::FileName b-or type NotifyFilters::DirectoryName * Only watch text files. set watcher::Filter to "*.txt" * Add event handlers. attach method OnChanged as type FileSystemEventHandler to watcher::Changed attach method OnChanged as type FileSystemEventHandler to watcher::Created attach method OnChanged as type FileSystemEventHandler to watcher::Deleted attach method OnRenamed as type RenamedEventHandler to watcher::Renamed * Begin watching. set watcher::EnableRaisingEvents to true * Wait for the user to quit the program. display "Press 'q' to quit the sample." perform until exit accept any-key if function upper-case(any-key) = "Q" exit perform end-if end-perform exit method end method. * Define the event handlers. method-id OnChanged private static. procedure division using by value #source as object, e as type FileSystemEventArgs. * Specify what is done when a file is changed, created, or deleted. display "File: " & e::FullPath & " " & e::ChangeType goback. end method. method-id OnRenamed private static. procedure division using by value #source as object, e as type RenamedEventArgs. * Specify what is done when a file is renamed. display "File: " & e::OldFullPath & " renamed to " & e::FullPath goback. end method. end class.

I got MySQL installed, but I think it would be more convenient for me to use the SQL I already got.

I am not quite sure what you are asking for here. In Visual COBOL you can connect to databases that have an ODBC driver for native code or an ADO.NET provider for .NET managed code or a JDBC connection for managed JVM code by using OpenESQL which is the Visual COBOL embedded SQL preprocessor. You can also connect to Oracle using Pro*COBOL and COBSQL or DB2 using the DB2 preprocessor and the DB2 ECM. This is covered in the docs here What is it exactly that you are trying to do? Thanks.

The select command may be executed directly through the SDK's CommandProcessor class, or indirectly through either stcmd or stcmdEx. The syntax of the command is select * | all | access-rights | changes | linked-items | enhanced-links | lifecycle | links | workrecords | agile-breakdown | scope-change | differences | historical-revisions | attached-labels | {propertyName, propertyName,...} | filter = 'filtername' from 'typeName' {history} {deleted} {backlog} {workspace} {between-labels labelname1 and labelname2} {attached-to-label labelname } {at [label = "label" | promotionstate = "promotion state" | datetime = "date" {-pattern "pattern"}] into fileName { separator 'field separator' } {newline newlineSeparator} {headers 'on' | 'off' | sqlnames} {toExcel} where {{ attached-label = 'labelName' } | { query = 'myquery' } | propertyName relation value and/or propertyName relation value and/or...} {for} {folder = 'myfolder' {recurse} or folder = 'myfolderhierarchy' {recurse} or folder = . {recurse}} or ...} order by {propertyName, propertyName,...} | orderFilter = 'myOrderFilter' [–epwdfile “passwordfilepath”] [-p "userName:password@hostName:endpoint/projectName/[viewName/][folderHierarchy/]"] Use the select command to invoke StarTeam meta-queries. The combination of options determines the type of query, which could be over a file, folder, change request or etc., and the saved filters for the type. Values that contain spaces should be enclosed in double quotes. This command has been modeled on the standard SQL SELECT syntax. Cross type joins are not supported. If folder identification clauses are not specified, the tool assumes the folderHierarchy is set through the setProject command or the root folder of the view, with recurse ON (that is, all descendants or depth == -1). The WHERE clause is constrained to a query and a possible set of folders. Folders may be combined with an OR, but cannot be joined with an AND. Folders act as a further constraint to a query. Folders potentially reduce the subset of results obtained from the query to the items that reside within the specified folders. When a folder hierarchy is specified in the WHERE clause of a select, update or delete statement, the path must start with the root folder and traverse the folder tree all the way down to the leaf folder of interest. It must be explicitly terminated by a \. However, the root folder path must not start with a \. / and \ are interchangeable. Simple dynamic queries support either chained OR clauses or chained AND clauses. However, they do not support a mix of OR and AND conditions. Complex queries are supported but only as saved queries, for example: where query = 'mySavedQueryname'. If a property name in the where clause identifies a text property, the relation is '=' and the value starts with a "*", then the * is treated as a wildcard targeted for expansion. This query returns all items whose property values end with the text of the query value. For example, the following returns all files in the view whose names end in .doc. Only * is supported as a wildcard, and can exist contextually at the start of, at the end of or surrounding a phrase. In other words, "*.doc", "doc*", or "*.*" will all expand the * out to mean - any set of characters. No other wildcard characters are supported. "." itself is treated as a literal character, no different than (say) a, b or c.  *  (| all ) specifies all defined properties for the type. (This is a superset of propertyName1, propertyName2, ...) propertyName {n} specifies a subset of properties for the type, identified by case insensitive internal names. relation  may be one of {=, , =, , =, , !=, in (,)}. Alternative equivalents are {eq, lt, lte, gt, gte, neq}. in  represents a mutli-valued set relationship, e.g. changenumber in (1,2,3,4). all the other relationships are single valued. e.g. changenumber = 1, changenumber 2 and changenumber 5 access-rights  overrides properties. If specified, it generates an access rights report. The columns are the set of available permissions. The rows are the Securable’s (or Container’s) for which access rights exist. agile-breakdown   overrides properties. If specified, it generates a breakdown of Sprints or Plans. Sprints For sprints, it is a denormalized join or view of all stories, tasks, and workrecords attached to the selected sprints. Each row represents the break down to the workrecord detail.  Plans For plans, it is a denormalized join or view of all requirements attached to the selected plans. historical-revisions  produces a report that identifies and lists all the revisions at which the items are actually attached to the label specified by attached-to-label. If historical-revisions is specified, then attached-to-label must be specified and the where clause is ignored. attached-labels  produces a report combining all historical revisions of the selected item(s) with the labels attached to each of those revisions. The rows of this report match the label tab details in the CPC. changes overrides properties. If specified, it generates a change package changes report. The columns identify revision details of each attached item to the change package. The rows identify the attached items. The report can span multiple change packages. scope-change  overrides properties. If specified, it generates a scope change report, targeted at measuring the total scope (cost) of the sprint. It includes the history of the sprint including all active/deleted stories associated with the sprint and the history of active stories, with their estimated points. scope-change can only be used in conjunction with the sprint type, differences  overrides properties. If specified, it generates a differences report for files (spanning all revisions) between two labels. Note: differences can only be used in conjunction with the file type. If the differences keyword is specified, then between-labels 'labelname1' and 'labelname2' must be specified, and the where clause is ignored. linked-items  Overrides properties. If specified, it generates a process item report. The columns identify revision details of all attached items to the process item. The rows identify the attached items. The report can span multiple process items. Each process item may be linked to multiple revisions of the same artifact (file, folder). enhanced-links  Overrides properties. If specified, it generates an enhanced links report, which provides trace visibility across all views in the project for which trace the queried items shares exist. The columns identify revision details of all attached traces to the queried item. The rows identify the attached queried items. The report can span multiple items.  links  overrides properties. If specified, it generates a links report. The query follows all the traces which lead to or away from the specified item and describes the details of the items at the other end point. lifecycle  overrides properties. If specified, it generates a report that tracks the item through its lifecycle (from creation, through moves and shares, to possible deletion). The rows identify all history and revisions per item, covering item changes, moves and deletes, ordered by modification time - from most recent to oldest. The report can span multiple items. The first column identifies the item by item id. workrecords overrides properties and can only be specified in conjunction with the Task type. When specified, a workrecords report will be produced. filter   overrides properties. It identifies a saved StarTeam filter (by name) for the specified type, and expands into a subset of properties for the type.  typeName Specifies the StarTeam item type. Types are mutually exclusive, and include any one of the stock or custom component (if any) types. at  describes a rolled back view configuration. It may be one of label, promotion state or datetime. If specified, the query is run at the rolled back configuration. datetime may be further qualified by a pattern. The pattern must match any valid pattern supported by the java JDK in java.text.SimpleDateFormat.applyLocalizedPattern(String) and ensure that embedded date/ time strings strictly adhere to that pattern. attached-label  specifies a label to which the items of the specified type have been attached. The items to be selected are the ones attached to the label. deleted  constraints the result set. If specified, only deleted items are returned. history is a qualifier on the result set. For example, if the result set contains ten items of a given type, history returns all revisions of each item. backlog  acts as a constraint on story queries. It identifies those stories (from a selected range) that are not linked to any sprint. workspace acts as a constraint on file queries. If specified, it locates not-in-view folders and files from the file system (the view path mapped to working folders on disk) and includes them in the report. folder specifies the StarTeam folder name in the current view. If there are multiple folders with the same name, the command returns all folders with that name. To explicitly qualify a given folder, specify the folder hierarchy in the "/" format. Start from the root folder and end in a branch folder. For example: /StarDraw/SourceCode/On-line Help/. recurse Designates all descendants from the folder specified. .  is a special case that implies the current working folder, requiring the query engine to find StarTeam folders with paths mapping to the current working folder. which further implies that the engine must be running inside the StarTeam folder hierarchy mapped to disk. into  "fileNameWithPath" specifies a file to which the output of the query will be written. The generated output is tabular in format, each row separated by a carriage return / line feed, specific to the platform the query is run on. newline  if newline separator is specified, then embedded new lines inside text fields are replaced by the provided separator. If not specified, then embedded new lines are replaced by their character string equivalents, specifically, "\r" and/or "\n". headers By default, headers are turned on. If headers = off is specified, output files are written without headers. A special case of headers turned on is to substitute the property internal names for the display names by further qualifying the parameter  sqlnames . toExcel  produces an output file which is in CSV format. The columns are separated by a comma and embedded new lines in text are replaced by line feeds. This is a special format which allows Microsoft Excel to successfully import these types of files directly into a spreadsheet while retaining the tabular structure of the data. myQuery  specifies a saved StarTeam query name for the type. It acts as the equivalent of a compound where clause of a SQL statement, such as a complex combinations of relations and operators. If no query name is specified, the command performs the action on all objects of the type. order by Specifies a default sort order for the output result set. OrderFilter  Specifies a saved StarTeam filter name for the type. It expands into a subset of properties for the type, which is used for sorting. myFilter and myOrderFilter can be different filters. The properties specified in myOrderFilter should not be set for grouping. If a set of property names is specified instead of the order filter, the sort criteria default to ascending order, sort by text is set for text properties, and sort by date is set for Date/DateTime Properties. If you need more specific sorting, specify an existing saved filter. -p Indicates the view or folder to be used and also provides the user name and password needed to access the StarTeam Server. specifically, -p "user{:password}@host:port/projectName/viewName} -epwdfile if a password is not specified in -p, then -epwdfile must be specified. Important: When used with select, update, insert, or delete, the command execution context is stateless. The position of -p in the statement is important. It must be located at the very end as the very last parameter of the command. Placement anywhere else in the query will produce indeterminate results, possibly leading up to an SDKRuntimeException. The position of -epwdfile is equally important, and must immediately precede -p. Note: For the Change Request type, the AddressedInBuild property can be used in the where clause of a query using the special value "Next Build" or "-2": Important note for use with stcmdEx. Enclose the greater than " " and less than " " characters within double quotes. By design, stcmdEx interprets the as a redirect to a file so, without  "" you get an error "The system cannot find the file specified". Several examples of the select syntax follow,,, select * from File where query = “Status = Current” order by orderfilter = “All Files By Status” –p “Administrator:Administrator@localhost:49201/StarDraw/Release 1.0 Maintenance” The following example shows how to use the differences keyword. It selects all properties of all change requests and writes them into a file called QueryOutput.txt. select differences from file between-labels 14.0.3.21 and 14.0.3.27 into “c:/temp/differencesReport.txt” separator | -p “username:password@hostname:port/project/view” select * from changerequest into “c:/temp/QueryOutput.txt” select linked-items from ChangeRequest where AddressedIn = “Next Build” or select linked-items from ChangeRequest where AddressedIn = “-2” The example below selects three properties, Name, Status, and File Time Stamp at check in, for all files, which satisfies the built in query Files to Checkin. select Name, Status, Modified from file where query = "Files to CheckIn" The example below selects all tasks from the Sales Materials folder or the Marketing Materials folder and its descendants. It returns a result set containing only the task properties described by the "By Status and Responsibility" filter. select * from task where filter = "By Status & Responsibility" select filter = "By Status and Responsibility" from task where folder = "Sales Materials" or folder = "Marketing Materials" recurse The following examples show how to use select with change requests and change packages. select linked-items from ChangeRequest into fullyQualifiedPathToOutputFile where ChangeNumber = 1234 –p “username:password@host:port/project/view” select changes from ChangePackage where name = "Workspace Changes on 2013-10-15@22-43-00Z" This example shows how to use the select command with the lifecycle parameter. select lifecycle from File into fullyQualifiedPathToOutputFile where FileName = Server.java -p "username:password@host:port/project/view" This example shows how to generate a workrecords report: select workrecords from task where StTaskNumber = 88 This examples shows how to generate an agile-breakdown report: select agile-breakdown from sprint into c:/temp/agileReport.txt separator "|" where SprintID = 1234 -p "user:password@host:port/project/view" The following example shows you how to select rows in a range: select "*" from changerequest into "c:/temp/stout.txt" where changenumber " " 50000 and changenumber " " 50100 -p "user:password@host:port/project/view" The next example uses a date range on the ModifiedTime property: select "*" from ChangeRequest into "c:/temp/stout.txt" pattern = "M/d/y" where modifiedtime " " 1/1/2014 and modifiedtime " " 8/30/2014 -p "user:pwd@host:port/project/view" The following example produces history results similar to the deprecated hist command: select revisionnumber, viewid, modifieduserid, modifiedtime, comment from file history -p "Username:Password@host:port/project/view/[folderhioerarchy]/" where name = "filename" this example shows the use of historical-revisions select historical-revisions from file attached-to-label "label name" -p "user:password@host:port/project/view" the next two examples show the use of wildcards and fully qualified folder paths select folder, name from file where name = "*.doc" for folder = "StarDraw\Source Code\External Resources\" select viewmemberid, name, description from file where name = “*.doc” the next few examples show different usage of property relation value(s) select * from ChangeRequest pattern = "M/d/y" where ModifiedTime 12/14/1999 and modifiedtime "2/16/1999" select * from ChangeRequest where ChangeNumber in (10298, 10310, 10316, 10320)"); select * from ChangeRequest where ChangeNumber = 10298 select * from ChangeRequest where ChangeNumber " =" 10298 and ChangeNumber " =" 10320 select * from File where name = "GNUmakefile.build*" select * from File where name = "*.buildinfo" select * from File where name = "*ranching release views.doc*" select * from ChangeRequest where Responsibility = "Alan Kucheck" note that " =" can be replaced by gte without the double quotes around it, = can be replaced by eq, etc. The select command continues to grow as new requirements are identified.

Hi Harald, We are aware of that issue. A work-around is to disable "Project Build Automatically" in Eclipse. This issue will be addressed in the Silk Test 16.5 release. Regards, Michael

Hi All,        Whenever i'm update the excel sheet it throws following error ." *** Error: (07002) [Microsoft][ODBC Excel Driver] Too few parameters. Expected 1.  "using silk  4test script ,  how to i resolve it,  At the same time i'm updating particular row in the excel sheet at the time also i'm getting this error... it shows below error : " *** Error: (07002) [Microsoft][ODBC Excel Driver] Too few parameters. Expected 2.     [ ] sSQL3 ="update `Sheet1$` set status=('unknown') where name=('sat');"    [ ] hSql3 = DB_ExecuteSql (hDB1, sSQL3) i have written this update query:   [ ] STRING sSQL ="update `Sheet1$` set Result=('unknown');"   [ ] HANDLE hSQL = DB_ExecuteSQL (hDB,sSQL) below error: *** Error: (07002) [Microsoft][ODBC Excel Driver] Too few parameters. Expected 1.    Any one having idea means please share it ..... thanks, Sat6804      

I have seen that error when the query contains a field name that cannot be found, check that the fields exist in the sheet.

Thanks, helped a lot, but if I need to set a folder (directory), as could be done, already much but thank you. Always remembering that the translation is Google

Hi We have a customer running thin client at Faroe Island and the Acurcl is based on our server in Copenhagen, version 9.2.1 and they are complaining about the performance. Of course it is the connection, and the y have a connection with 20 Mbit Down   and 10 Mbit up , but a slow ping  (around 65 ms). How much does this Ping influence in the performance. I have read about  AGS_RECEIVE_BUFFER_SIZE and AGS_SEND_BUFFER_SIZE  but I can't se any changes in performance, when I change these settings. Has anybody got similar problems with slow Ping, and how have you optimized your system. Is it possible to reach a satisfied performance with such a slow Ping ? Does anybody know a good way to measure performance in a thin client environment ? Best Regards Steen

I did have an extra underscore in my code but after removing it I still get the COBCH1623 error.

We have recently seen our Cobol program calls to Assembler sub-programs abend with a S0C5. We changed our default for a mainframe dialect from AMODE(31) to NOAMODE for performance reasons and started issuing the S0C5 abend to highlight an address incompatibility when Cobol CALLs an Assembler sub-program and the AMODEs do not match. Depending on if one is debugging or running an application, the error might show up as a RTS200, a message in the Assembler debugger saying 'Questionable exit from address space' or a S0C1 abend. Re-compile the Cobol programs that will call Assembler to use AMODE(31) or AMODE(24) depending the expected AMODE for the application. If possible, use it for all programs in the application.    Additional Keywords: IFD-005W Program-Interruption Operation exception IDF-106I Questionable exit from address space

 We have encountered various MFBSI errors: 209 211 228. We have had performance issues, system slows down, transactions stop responding, jobs are running very slow and are stuck in the JES Input queue, and jobs are taking more time to send a spool file to the printer using the printer exit module.      After examining log and diagnostic files from different customers and hearing back from their IT departments, we have found a variety of problems pointing back to the Symantec Endpoint Protection (SEP) antivirus software. There may be other antivirus software also causing such errors but at this time since it is very popular, our reports were for Symantec Endpoint Protection. Customers have given us the following descriptions and steps they took in trying to isolate the problems.   After disabling our Symantec Endpoint Protection (SEP) antivirus software, the intermittent but frequent Micro Focus related problems we were experiencing for many months seem to have disappeared. SEP does cause problems for us on non-Micro Focus servers but it also gives our Wintel team grief at times. SEP is installed and is doing its job on over 500 of our servers. SEP was installed on our production Micro Focus ES server before we went live last year. We ran for just over six months and then we started experiencing various MFBSI errors at different times: '209 Job submission failed', '211 Job Ended' and '228 Server crashed/killed when job was running'. We also saw communications errors in our Log.Html file. They were Windows socket errors: 'CCITC32-0015E A CCITCP transport failure has occurred. (CCI 15, Ext 10054) Conversation closed by client or failed due to broken network connection' and 'CCITC32-0015E A CCITCP transport failure has occurred. (CCI 15, Ext 10053) Conversation closed by client or failed due to broken network connection'. All of these errors pointed to timeouts and communication failures. We also experienced what many users perceived to be 'system hangs'. We now believe and have believed for some time that there was a common thread responsible for the problems just described. It is our feeling that this common thread is some sort of communication problem that caused the 209 timeouts and also prevented new work from entering the system via web services (i.e. the perceived 'hang' problem). When we checked the Microsoft event viewer, we would see events for SEP but they very often did not match up with our Micro Focus related errors. The events we did see did not lead us to believe SEP was the culprit as most of the events that SEP logged seemed to be quite innocuous (e.g., a simple signature file download). It seems that many times SEP would perform some task like a product update download but because nothing was 'updated', SEP did not log an event. After we removed Symantec Endpoint Protection from all of our Micro Focus ED and ES servers and from our SQL servers that Micro Focus communicates with, it seems that disabling SEP has caused our problems to disappear and it has now been the better part of two weeks since we have seen any MFBSI 209 errors or 'hangs'.

I was trying to test out some code in regards to the date in Visual Studio Cobol and I temporarily changed my system date on my computer. Now when I try to start VS I get "Unable to obtain the requested license Error 26: Request denied due to clock tamper detection". Is there anything I can do to fix this problem? The email I used to activate VS Cobol is tye_huggins@stu.indianhills.edu. Thanks for any help.

Problem: Installation of  Net Express or  Server for COBOL fails with the following error after hitting Next from the Welcome screen: "error 1606 Could not access network location \\MachineName\ShareName\FolderName" Resolution: It appears Microsoft Installer needs to validate the locations that are specified for the following registry keys before starting the actual installation: Personal My Music My Pictures My Video These registry keys are found from  HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders, and they need to point to a valid location. Here are their respective value by default: Personal %USERPROFILE%\Documents My Music %USERPROFILE%\Music My Pictures %USERPROFILE%\Pictures My Video %USERPROFILE%\Videos

Hi, I have created a script which consists of start and stop 3 systems repeatedly , The first application is installed on one PC and two  applications are installed on the  same PC. The script is runnig correctly but after a while this error is displayed:"Open Agent Communication Thread is paused.  No agent requests possible."  Can someone tell me this error is related to which issue..?    Thank you  

Hello Ghania Please log a support incident. The problem you are describing was fixed in Silk Test 16.0 Hotfix 2 (16.0.2.7495) but if you are still seeing it then we need to find out why.

I am trying to move some scripts from one database to another via Silk Workbench 16. I have exported them out of the first database. When I attempt to import them into the 2nd database, the application crashes.   These are the messages I am getting from the event viewer.   application name: SilkTest.exe, version: 16.0.0.7468, time stamp: 0x54f99a97 Faulting module name: TPUtils.dll, version: 16.0.0.7468, time stamp: 0x54f99b58 Exception code: 0xc0000005 Fault offset: 0x0002c9f0 Faulting process id: 0x1488 Faulting application start time: 0x01d0bda8f5f6ad51 Faulting application path: C:\Program Files (x86)\Silk\SilkTest\ng\gui\SilkTest.exe Faulting module path: C:\Program Files (x86)\Silk\SilkTest\ng\gui\TPUtils.dll Report Id: a2398d21-299c-11e5-815f-4437e63fb14c and Application: SilkTest.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 6B9BC9F0 Stack: Any idea what is going on? It seems to be hanging on some scripts but does others.

Hello Tye Huggins, Someone will reach out to you by email from Micro Focus Customer Care to help resolve your issue.

acuthin --ping server-name:port will give you a dialog of how long acuthin takes to get to the server and back