Rocket® COBOL

Is there a library routine to get the User-ID or name from a Print file that a User has Created?As the new normal is working from Home users want to just view there own print files which are in a spoollib folder.I have looked @ I$IO and C$Fileinfo to no avail unless I missed something. 

RM/COBOL v10.01 on Windows 7 and 10. Users are receiving the following error in LCS when attempting to create a letter.I've checked the documentation.  Although I found that the run-time error 91 is a Server Error, it doesn't tell me much else.Has anyone else had this issue? Thanks,Linda

I noticed that negative numbers seem to be sort of encoded by Visual COBOL when written to line sequential files. PIC S99 VALUE -2, for instance, is stored in a line sequential file as "0r": Is this by intention? I couldn't find any documentation describing how negative numbers are stored in line sequential files. Until now, I would have believed they were stored like any other literal value (e.g. as "-02").Just in case, please find a sample project attached, depicting the issue.Your help is appreciated.

I noticed a setting in the COBOL project settings that may clash with other projects in a Visual Studio solution when compiling for x64 processors: Apparently, the Visual Studio 2019 MSBuild platform target (1) is ignored while at the same time a proprietary Platform Target property (2) has been added in project settings.From what I can see so far ...the proprietary setting is pointless as it is ignored by the compiler(i.e. no compiler settings are changed when this value is changed (see Build Settings text field at the bottom of the COBOL settings page))no MSBuild platform target is available for x64 in the solution (1)The compiler appears to compile to the MSBuild platform target (3), ignoring the proprietary setting (2)As a beginner to COBOL (particularly to Visual COBOL) I'm anything but sure and I'm not able to set-up a sample solution at this time; yet, adding a 64 bit .NET project to this solution and adding dependencies to the COBOL project should result in failure

Hi Chris,allow me to ask for 2 questions:1. is it possible to use T-SQL commands between exec SQL and end-exec?    When yes, how to make the difference between SQL code and T-SQL code2. How must we convert the Netexpress *.RC filesI see as error Directive /R invalid or not allwed here for the *.rc filesand illegal command line (COBOL)Thanks for your great help, allowing us to advancing in visual Cobol!

During my debug session I want to follow what's written to an OUTPUT file in Visual Studio.To do this, I step into my code, shortly after the OPEN OUTPUT statement, and try to open the file in Visual Studio.But Visual Studio refuses to open the file. It reports that the file is "in use by another process". Same does every other application being able to open a file with read-only access.I don't seem to be able to give correct parameters to the OPEN OUTPUT statement. I tried "OPEN OUTPUT SHARING WITH READ ONLY". However, whenever the file is created, it it's never created with FileShare.Read access (see screen recording attached to this message).What am I doing wrong?Your help is appreciated.

Problem A simple CONNECT that works fine on Oracle 11g fails with ORA-12560 on Oracle 12c and higher. It appears the trailing spaces on user id and password are no longer trimmed causing the connect to fail, and the result is the same with PICX=CHARF or PICX=VARCHAR2. Solution As of Oracle 12cR1, this is the new behavior of Pro*COBOL – trailing spaces in the password are not removed. In order to accommodate this change, Oracle introduces a new option "trim_password" to Pro*COBOL as of 12cR1. However, this option is never mentioned in the Oracle documentation until the Release Note in 12cR2:https://docs.oracle.com/en/database/oracle/oracle-database/12.2/pcbrn/index.html#PCBRN-GUID-D345B73E-3C0D-4B0E-8BA1-0D5EA8442AAF\\ By default on Windows, trim_password is set to NO, whereas it is set to YES on Unix/Linux. You may then do one of the followings: Add the trim_password option into COBSQL:P(COBSQL) END-C trim_password=yes ENDP​ Update the default value of trim_password to

in netexpress 5.x i have use any copy-files for my development as:wingdi.cpy, miniwin.cpy, wintypes.cpy, winuser.cpyYes, i can use this files for compiling in Visual Cobol, but are there newer copy-files or was this files missed to be included in VC5.xI used up7Thanks for your help!

  #COBOL60 – Shaping the Future of Core Business Applications, Live Webinar am 12. Mai 2020, 10 Uhr Gemeinsam mit dem Meinungsforschungsinstitut Vanson Bourne haben wir Unternehmen zu Markttrends & geschäftlichen Herausforderungen befragt, denen sie sich im Zeitalter der Digitalisierung mit COBOL stellen müssen. Die Ergebnisse in diesem Webinar! #Webinars#DigitalisierungmitCOBOL#COBOL#BusinessApplication

i have converted a netexpress 5.x Project to Visual Cobol to generate a lbr and dllafter converting, i become a error by compiling in dll -> "Can't open Input file oopss.libWhen i take away the oopss.lib in the field link with lib's, i become following error:unresolved external Symbol _oopsverifyobjectChris, what is to do?Thanks very much!

Any Documentation for color FAC assigned to a field somewhere?Currently if I Move this value of 10135429 to the FAC of a field it will change the color to RED.Wondering what other combinations are available.

Hello,Can someone help me and translate these C# instructions to Cobol? public Form1(){     InitializeComponent();     this.FormBorderStyle = FormBorderStyle.None;      this.DoubleBuffered = true;     this.SetStyle(ControlStyles.ResizeRedraw, true);}Rectangle Top1 {     get {          return new Rectangle(0, 0, this.ClientSize.Width, 10);     }}protected override void WndProc(ref Message messages){     base.WndProc(ref messages);     if (messages.Msg == 0x84) // WM_NCHITTEST     {          var cursor12 = this.PointToClient(Cursor.Position);          if (Top1.Contains(cursor12)) {               mess

Integrative Designansätze für die COBOL-Entwicklung : Application Workflow Modeller in der Praxis   An einem praktischen Beispiel wird das Konzept des Application Workflow Modellers (AWM) erläutert und die Entwicklungsumgebung von Visual COBOL / Enterprise Developer for Eclipse um zusätzliche Funktionalität erweitert.   #COBOL#applicationworkflowmodeller#AWM#Videos

Integration der COBOL Entwicklungsprozesse mit dem Application Workflow Modeller   Ausgehend von den gestiegenen Anforderungen an die Software-Entwicklung und einer kurzen Erläuterung des DevOps-Ansatzes wird das Konzept des Application Workflow Modellers (AWM) dargestellt, mit dem die Funktionalitäten der Eclipse IDE in den genannten Micro Focus-Produkten mit wenig Aufwand an die individuellen Bedürfnisse der jeweiligen Entwickler-Teams angepasst werden können. • Integrative Ansätze in der Software-Entwicklung • Kurze Einführung in DevOps-Konzepte • Idee der Modellierung benötigter Funktionalität mit AWM • Erläuterung an einem Kundenbeispiel   #COBOL#applicationworkflowmodeller#Videos

Problem: When compiling an application under Net Express, which uses a "Currency" symbol of "£" in the code it works OK, but when compiling it under Server Express 5.0 it displays the following compilation error messages;    130     currency sign is "ð". *1004-E****************************************************************(   0)* **    Continuation character expected. End of literal assumed. * 120-S********************                                            (   4)* **    Illegal currency symbol   1620 01  w-edit-ret       &nbsp

Hello, can you help me with the following problem? We have an old client / server application using C / S Binding technology (client=Windows, server=linux or windows). We use Net Express and Server Express for development. Now we want to migrate to the Visual Cobol 5.0.What tools do you recommend? Is Visual Cobol Development Hub 5.0  a standalone product or I need to have a Visual Cobol 5.0 for Visual Studio 2017 or for Eclips? Is C/S Binding technology a part of mentioned products? If not,  is it available for free download or is it necessary to buy it?Thank you for your answers, Petr 

After I've updated VS2019 to its latest updates and Help library contents, Micro focus Visual cobol documentation section disappeared even from intlisense I've tried the repair method on bot files (vsvc5*.exe and vsvc5_u*.exe) then chose repair.but nothing changed and documentation still not therehow can get the documentation back?I have found similar situation here:/cobol/visualcobol/f/forumid-18/116076/f1-leads-to-cannot-find-requested-topic-on-your-computerBUT the suggested file to be downloaded and extracted is no foundable by me vc50docsvs2019.zipI have tried both microfoucs.com search and google.com search and I could not find it

Currently, when declaring data items, it's sometimes a hassle to declare the correct data item size: I'd like to propose to add a Quick Action to warning COBCH1007 (and similar warnings/errors) that's updating the PICTURE clause according to the provided value. For textual values there may be a list of suggested Quick Actions provided by the proposed feature from which the user may choose. This list may provide options like:X(n)A(n)XXXXXXX...AAAAAAA...For numerical values the corresponding "S" or "9" values should be added ("9" either left or right to an optional "V" PICTURE clause spec).I'm not sure if there are a set of rules for edited numerical values that can be derived from a VALUE clause. If so, there may be a list of suggested Quick Actions provided by the proposed feature from which the user may choose, too.#FeatureRequests#QuickAction

If I place the cursor on W900-CUR and press Shift F12 Visual COBOL won't find any references. However, if I search for W900-CUR I will clearly see that the variable is used throughout the programme. Is this by design?EXEC SQL BEGIN DECLARE SECTION END-EXEC.01 W900-CUR SQL-CURSOR.EXEC SQL END DECLARE SECTION END-EXEC.

Hi PeopleAn Acu4GL START, we populate the where clause unconditionally effectively the where clause built is :           INTEGLOG_STATUS = 'C'  AND INTEGLOG_SYSTEM = 'EDMS'      We are running a single thread and therefore have not felt the need to wrap LOCK THREAD and UNLOCK THREAD around the START as we have in many other cases.This process runs daily and has twice failed on the START with 9D156. Would wrapping LOCK THREAD, UNLOACK THREAD around the START provide any protection?  Full body of code is .....     INITIALIZE POSINTEGLOG-REC.    MOVE 0 TO WS-COUNT-1    MOVE "C" TO POSINTEGLOG-STATUS.    MOVE "EDMS" TO POSINTEGLOG-SYSTEM.* the following START has on 2 different occasions failed with 9D156    PERFORM START-POSINTEGLOG-STATUS-SYSTEM-KEY    IF WS-STATUS NOT = "00"

9d156 sql error on START in Acu4GLI have instances where a simple START with where constraint is failing with 9D156 complaining there is an error near "AND"The code is pasted below, but essentially we setup a where clause before executing the startINTEGLOG_STATUS = 'C' AND INTEGLOG_SYSTEM =  'EDMS'We are running in  a single thread so would not expect to need to LOCK THREAD and UNLOCK THREADeither side of setting the where clause and doing the start.  Would using the LOACK THREAD help prevent 9D156? ...here is actual code    INITIALIZE INTEGLOG-REC.    MOVE 0 TO WS-COUNT-1    MOVE "C" TO INTEGLOG-STATUS.    MOVE "EDMS" TO INTEGLOG-SYSTEM.* the following START has on 2 different occasions failed with 9D156    PERFORM START-INTEGLOG-STATUS-SYSTEM-KEY    IF WS-STATUS NOT = "00"     &nbs

Problem The K4 runtime switch is not documented in Visual COBOL for Visual Studio. Solution The K4 runtime switch (i.e. COBSW= K4) is a holdover from the old COBOL Workbench product. Although it is not documented in Net Express and Visual COBOL for Visual Studio, it is still a valid COBOL runtime switch. The purpose of this runtime switch is to cause runtime system error messages to stay on the screen until a key is pressed. This is useful in batch runs where you want to know if any program terminates with a run-time system error message, or in a system that displays menus, where run-time system error messages can sometimes be quickly overwritten. The description of this runtime switch has been added to the documentation of Visual COBOL 6.0 for Visual Studio. Note: This is already available in the documentation of Visual COBOL for Eclipse.

Problem: In Visual COBOL 4.0 and Visual COBOL 5.0, in an extremely small and limited set of cases, there is an issue running older .NET executables and dll, and older JVM .class files. Specifically, for the problem to occur, ALL of the following must be true. Your application must do an IS NUMERIC condition test on a variable declared with USAGE NATIONAL. The code being run must have been created with Visual COBOL 3.0 or earlier. The code must be run using Visual COBOL 4.0 or 5.0. The problem is that the IS NUMERIC test may give the wrong answer. Solution: The resolution is to recompile any program that uses this construct. In order to resolve this issue fully, in Visual COBOL 6.0 the .NET and JVM COBOL runtimes will reject any program using IS NUMERIC on a NATIONAL item that was compiled with an earlier (i.e. 5.0 or earlier) product, issuing a “missing method” exception. The resolution is to recompile. For the avoidance of doubt, if a program does not use NATIONAL data, it is compl

When the cursor is set to an empty line in the editor, the [HOME] key currently always sets the cursor to the leftmost character of the left margin.I'd like to suggest to have the [HOME] key toggle the current cursor position between the leftmost character of the left margin and the first column right to the left margin (the first coding position) on empty lines (see animated GIF image attached). This behaviour would/should mimic the existing behaviour of the [HOME] key on non-empty coding lines.The suggested behaviour would be helpful, increasing coding speed.

I noticed that with Visual COBOL for Visual Studio 2019 TABs are not retained even though the settings in Tools > Options > Text Editor > Micro Focus COBOL > Tabs are set to use the Horizontal Tabulator character for spacing (see images attached). Doing so, Visual COBOL always misaligns new lines to existing lines with above settings in place.Micro Focus Visual COBOL - Options.pngMicro Focus Visual COBOL - Not inserting TABs.gif