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 | {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. 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.

I doubt that.I am speaking of 2 physically separate machines. one a controller and the other an agent .

Hi Camille, a configuration is a combination of (execution server) keywords and parameters. Where (execution server) keywords are just some kind of tags that are then visible during the test execution (might be necessary to enable the information in the manual test execution window via the gearwheel). The sequence of tags can be anything you need to describe the environment where your tests should be executed in more detail. In our internal testing - where we have to test different languages, different browsers, different databases,  and different web servers - sample configurations are: English, Firefox, SQL2012, Tomcat German, IE, Oracle 11g, IIS and so on. Does this answer your question? Regards, Florian

Here is a small program that I wrote that will recursively list all folders, subfolders and files within those folders using native Visual COBOL. Use and modify as required: identification division. program-id. testscandir. environment division. configuration section. data division. working-storage section. 01 f-entry. 03 f-attribute pic x(4) comp-5. 03 f-date-stamp. 05 f-year pic x(4) comp-5. 05 f-month pic x(2) comp-5. 05 f-day pic x(2) comp-5. 05 f-hour pic x(2) comp-5. 05 f-minute pic x(2) comp-5. 05 f-second pic x(2) comp-5. 05 f-millisec pic x(2) comp-5. 05 f-dst pic x comp-5. 05 f-size pic x(8) comp-5. 05 f-name. 07 f-max-len pic x(2) comp-5. 07 f-entry-name pic x(1024). 01 scan-pattern. 05 pattern-len pic x(2) comp-5 value 0. 05 pattern-text pic x(256) value spaces. 01 scan-attrib pic x(4) comp-5 value 1. 01 scan-flags pic x(4) comp-5 value 2. 01 scan-status pic x(2) comp-5 value 0. 01 scan-entry. 05 entry-attrib pic x(4) comp-5. 05 entry-date-stamp. 10 e-year pic x(2) comp-5. 10 e-month pic x(2) comp-5. 10 e-dow pic x(2) comp-5. 10 e-hour pic x(2) comp-5. 10 e-minute pic x(2) comp-5. 10 e-seconds pic x(2) comp-5. 10 e-mill pic x(2) comp-5. 10 e-dst pic x comp-5. 10 e-filesize pic x(8) comp-5. 10 e-filename. 15 e-name-len pic x(2) comp-5. 15 e-name-text pic x(1024). 01 next-pattern pic x(1024) value spaces. 01 sub1 pic 9(9) value zeroes. 01 any-key pic x. local-storage section. 01 scan-handle pointer. 01 prev-pattern pic x(1024) value spaces. procedure division. display "enter starting dir name; e.g. C:\TEMP" accept next-pattern move 0 to pattern-len move 3 to scan-attrib move 2 to scan-flags call "do-scan" display "complete" accept any-key goback. entry "do-scan". move next-pattern to pattern-text perform varying sub1 from length of pattern-text by -1 until sub1 = 1 if pattern-text(sub1:1) not = " " move "\*.*" & x"00" to pattern-text(sub1 + 1:) exit perform end-if end-perform initialize f-entry move length of f-entry-name to f-max-len display "folder = " pattern-text(1:70) accept any-key call "CBL_DIR_SCAN_START" using by reference scan-handle, by reference scan-pattern, by value scan-attrib, by value scan-flags, returning scan-status end-call perform until exit move spaces to f-entry-name call "CBL_DIR_SCAN_READ" using by reference scan-handle f-entry returning scan-status end-call if scan-status = 0 perform 100-remove-quotes * Is a folder? if f-attribute b-and 2 = 2 if f-entry-name not = "." and not = ".." move next-pattern to prev-pattern perform varying sub1 from length of f-entry-name by -1 until sub1 = 1 if next-pattern(sub1:1) not = " " move x"00" to next-pattern(sub1 + 1:) exit perform end-if end-perform string next-pattern delimited by x"00" "\" f-entry-name delimited by size into next-pattern end-string * recursive call for next folder level call "do-scan" display "return" move prev-pattern to next-pattern else display "folder = " f-entry-name(1:70) accept any-key end-if else display "file = " f-entry-name(1:70) accept any-key end-if else call "CBL_DIR_SCAN_END" using scan-handle goback end-if end-perform. 100-remove-quotes. perform varying sub1 from 1 by 1 until sub1 = length of f-entry-name - 1 if f-entry-name(sub1:1) = '"' move f-entry-name(sub1 + 1:) to f-entry-name(sub1:) end-if end-perform. end program testscandir.

Hi Arka. If you have found a bug please log a support incident and we will formally address it.

The error message is like this: C0000005 Access Violation at: 00BDF8F2 01:00068E8F2 c:\Program Files(x86)\Micro Focus\Mainframe Express\Base\Bin\MFPAMG.DLL Please help.

Sorry, wrong forum.

The error message is something like this: C0000005 Access Violation at: 00BDF8F2 01:00068E8F2 c:\Program Files(x86)\Micro Focus\Mainframe Express\Base\Bin\MFPAMG.DLL (The text between "at:" and "c:\" vary from time to time. Probably some memory address.) Please help.

Hello Shatty, It would be very helpful if you simply do a "Reply" from the last comment you received from the original post you made. This way, everything is kept in one place. Regards,

Posted by Shatty on Jul 9, 2015 13:32 Kindly would you tell me how to do the repair ?? is the  uninstall  ((uninstall  programs  in Control panel)) ??. what  about If I do reinstalling of Windows 7?? as far as MFC42.dll is a part of Windows OS

Hello Shatty, Here are the steps to do a repair on Windows 7 and Windows Server 2008: 1. Go to Control Panel Program and Features 2. Right-click on Micro Focus Net Express 5.1 3. Click Repair 4. Click Yes to allow NXP32MSI to update software Here are the steps to do a repair on older Windows platforms: 1. Go to Control Panel  Add or Remove Programs 2. Select Micro Focus Net Express 5.1 3. Click on Change 4. Click on Next 5. Select Repair 6. Click on Next 7. Click on Install Regards,

Thank you Scot - I do have time to discuss this now - I did open a ticket with Microfocus - 2831385. I was not sure how to call you direct. Our Architects believe we should be able to call a 1.6 jar from a 1.8 executable but not the other way around so would like to discuss any workarounds.

This line of code gives the error "COBCH1623: Anonymous method or method group cannot be cast to type DevExpress.XtraPrinting.CreateAreaEventHander.": ATTACH METHOD link__CreateReportHeaderArea to link::CreateReportHeaderArea This is the C# code that I'm converting to Visual COBOL:       private void btnPrint_Click(object sender, EventArgs e)         {             IPrintable component = gridControl1;             PrintableComponentLinkBase link = new PrintableComponentLinkBase()             {                 PrintingSystemBase = new PrintingSystemBase(),                 Component = component,             };             link.CreateReportHeaderArea += link_CreateReportHeaderArea;         }         private void link_CreateReportHeaderArea(object sender,         CreateAreaEventArgs e)         {             string reportHeader = "Categories Report";             e.Graph.StringFormat = new BrickStringFormat(StringAlignment.Center);             e.Graph.Font = new Font("Tahoma", 14, FontStyle.Bold);             RectangleF rec = new RectangleF(0, 0, e.Graph.ClientPageSize.Width, 50);             e.Graph.DrawString(reportHeader, Color.Black, rec, BorderSide.None);         } I don't get the error in C#, just COBOL, and I am not able to subscribe to the CreateReportHeaderArea event.  Any ideas on how to get this working?

There is a mode to execute the scripts of the SilkTest in the HP ALM? I'd like to export the results and the screenshots too. I saw that exists the test type 'VAPI-XP' in the HP ALM, but I'd like more informations about this integration.

What Silk Test client are you using?

I'm using the SilkTest Workbench version 16.0.

Check out STW.EXE , this is a command line tool that allows you to execute scripts (.Net scripts, Visual test and Keyword tests).

Hi Phil, What does the method signature for link__CreateReportHeaderArea  look like in COBOL?

      method-id link_CreateReportHeaderArea final private.       procedure division using by value sender as object e as type CreateAreaEventArgs.           goback.       end method. Intellisense shows me the error even if I have this method commented out.

Is it just a typo that you have two consecutive underscores in the name in the ATTACH statement or is that the actual problem? "link__CreateReportHeaderArea"