support: Customer Portal
Focused on delivering choice, investment protection and flexibility to organizations with valuable COBOL assets
 

Veryant Knowledge Base
Home > All Categories > isCOBOL General > Guide to Updating the isCOBOL Software Version in a Standalone, Fat Client or Thin Client Production Environment
Question Title Guide to Updating the isCOBOL Software Version in a Standalone, Fat Client or Thin Client Production Environment

A common topic to all three scenarios is the update of the license.
When your update is for a later year release (ex: 2021R# to 2022R#), then you need to request licenses for your products for that year and update the properties file containing your license keys.
To learn more about licenses, review the video on Veryant's YouTube channel: https://youtu.be/R6ScVpdT1XM.

1) Updating the isCOBOL production environment in standalone mode
If you are installing a later build of the same release (ex: 2022R1_1060.5 to 2022R1_1060.8), the setup program will install in the same folder and that's it, you do not need further steps to continue working.

If you are installing a different release, it would install in a different folder by default, though an alternative case is to have a generic folder for the installation (without the release number).

Example with the same folder name:
You had the 2021R1 runtime in c:isCOBOL
You install the 2022R1 runtime in c:isCOBOL

Example with different folder names (default):
You had: C:VeryantisCOBOL_SDK2021R1
And you update to: C:VeryantisCOBOL_SDK2022R1

On Windows if you are installing in the same generic folder then you can install on top of the old version and there are no further steps.

On Linux if you want to install in the same generic folder, you will first install in a different folder name (usually the default) and then move the installed files and folders from there to the generic folder.
After that no further steps are needed.

If you install the new isCOBOL version in a different folder name (default) and want to keep that different folder name, then you have to update the scripts you use to start your application, so they point to the new installation.
For example: (example for 2022R1 and JDK 8u321):

Windows

set ISCOBOL=C:VeryantisCOBOL_SDK2022R1
set ISCOBOL_JRE_ROOT=C:Program FilesJavajre1.8.0_321
set CLASSPATH=%ISCOBOL%lib*;%ISCOBOL%jars*;%ISCOBOL_JRE_ROOT%lib*;%CLASSPATH%
PATH=%ISCOBOL%in;%ISCOBOL_JRE_ROOTin;%PATH%
Linux
export ISCOBOL=/opt/veryant/isCOBOL_SDK2022R1
export ISCOBOL_JDK_ROOT=/opt/jre1.8.0_321
export CLASSPATH=$ISCOBOL/lib/*:$ISCOBOL/jars/*:$ISCOBOL_JRE_ROOT/lib/*:$CLASSPATH
export PATH=$ISCOBOL/bin:$ISCOBOL_JRE_ROOT/bin:$PATH
On Windows you have the option to set the system environment variables during setup rather than having to set them in each start-up script.
Just respond 'Yes' when the Installation Wizard asks that question during setup.
You can further edit those computer environment variables later to remove references to the prior version.

The last scenario for this case is if you copy/paste the isCOBOL folder structure from another computer to your standalone production computers instead of using the setup program.
  • You can copy/paste to a generic folder name be done.
  • Or you can copy/paste that structure to a new folder name and change scripts or update the computer environment variables manually as described above.
The usual folder structure to copy in this scenario is the /lib, /bin and /jars subfolders of the isCOBOL installation, though if you normally include other subfolders then continue doing so.

2) Updating the isCOBOL production environment in Fat Client mode
In this environment the isCOBOL File Server and data files are on a central server and the isCOBOL runtime with all the programs of your application are installed on every client.

If the server is Windows and you use the Windows Service for the isCOBOL File Server, first uninstall that service using this command:

   isserver -uninstall
. Then use the setup program to install the new release and have it enable/install the Windows service for the file server on the same port as before.

If the server is Linux/Unix and you use the daemon for the isCOBOL File Server, stop the daemon with the command:
   isserver stop
Then use the setup program to install the new release and restart with the command isserver start.

If you start the File Server with a script, stop/kill the file server first and then install the new release in a new folder or the same folder as explained in section 1.
If you use the same installation folder then no further steps are needed before running the script to start the file server.
If you are using a new installation folder, update the script to point to the new installation folder before running that script.
For instance (example for 2022R1 and JDK 8u321):

Windows
set ISCOBOL=C:VeryantisCOBOL_SDK2022R1
set ISCOBOL_JRE_ROOT=C:Program FilesJavajre1.8.0_321
set CLASSPATH=%ISCOBOL%lib*;%ISCOBOL%jars*;%ISCOBOL_JRE_ROOT%lib*;%CLASSPATH%
PATH=%ISCOBOL%in;%ISCOBOL_JRE_ROOTin;%PATH%
Linux
export ISCOBOL=/opt/veryant/isCOBOL_SDK2022R1
export ISCOBOL_JDK_ROOT=/opt/jre1.8.0_321
export CLASSPATH=$ISCOBOL/lib/*:$ISCOBOL/jars/*:$ISCOBOL_JRE_ROOT/lib/*:$CLASSPATH
export PATH=$ISCOBOL/bin:$ISCOBOL_JRE_ROOT/bin:$PATH
Here again, if the server installation is on Windows and you use the computer environment variables, then you can have the setup program to update those variables for you (or you update them manually in the computer's environment variables if you do not use the setup wizard) and no further changes to any script is needed before restarting the file server.

To update the client's runtime and the client's application programs you can use the isupdater utility, which is explained in more detail in Veryant's documentation.

3) Updating the isCOBOL production environment in Thin Client mode
In this scenario, you have the isCOBOL Application Server, the application programs, and data files on a central server or servers and the clients only have the thin-client runtime installed.

If the server is Windows and you use the Windows Service for the Application server, first uninstall that windows service using this command:

    isserver -uninstall
Then use the setup program to install the new release and have it enable/install the Windows service for the Application server on the same port as before.

If the server is Linux/Unix and you use the daemon for the Application server, stop the daemon with the command:
    isserver stop
Then use the setup program to install the new release and restart with the command:
    isserver start
If you start the Application server with a script, then stop/kill the Application server first and install the new release in a new folder or the same folder as explained in section 1 above.

If you use the same installation folder then no further steps are needed before running the script to start the Application server.


If you are using a new installation folder, update the script to point to the new installation folder before running that script. For example: (example for 2022R1 and JDK 8u321):

Windows
set ISCOBOL=C:VeryantisCOBOL_SDK2022R1
set ISCOBOL_JRE_ROOT=C:Program FilesJavajre1.8.0_321
set CLASSPATH=%ISCOBOL%lib*;%ISCOBOL%jars*;%ISCOBOL_JRE_ROOT%lib*;%CLASSPATH%
PATH=%ISCOBOL%in;%ISCOBOL_JRE_ROOTin;%PATH%
Linux
export ISCOBOL=/opt/veryant/isCOBOL_SDK2022R1
export ISCOBOL_JDK_ROOT=/opt/jre1.8.0_321
export CLASSPATH=$ISCOBOL/lib/*:$ISCOBOL/jars/*:$ISCOBOL_JRE_ROOT/lib/*:$CLASSPATH
export PATH=$ISCOBOL/bin:$ISCOBOL_JRE_ROOT/bin:$PATH
Again, if the server installation is on Windows and you use the computer environment variables, then you can have the setup program to update those variables for you (or you update them manually in the computer's environment variables if you do not use the setup wizard) and no further changes to any script is needed before restarting the Application server.

The application programs on the central server can be updated (if they were changed and/or compiled with the new release as well) by just FTPing the new application programs to the classes folder used on your central server.

To update the Thin-client runtime on every client, you should use the isupdater utility, which is explained in more detail in Veryant's documentation as well as in this video on Veryant's YouTube channel: https://youtu.be/ACzzsaEeY1c.

Authored by: Veryant Support This question has been viewed 473 times so far.
Click Here to View all the questions in isCOBOL General category.
File Attachments File Attachments
There are no attachment file(s) related to this question.
How helpful was this article to you?
User Comments User Comments Add Comment
There are no user comments for this question. Be the first to post a comment. Click Here
Related Questions Related Questions
  1. How do I compile for compatibility with older versions of Java?
  2. When can I get the "java.net.SocketException: Permission denied:connect" message? And how can it be avoided?
  3. How do I resolve "code too large for try statement" errors?
  4. How do I migrate indexed files to a format that is supported by isCOBOL?
  5. How do I prevent hackers from decompiling Java class files to reverse engineer my COBOL application?
  6. How can I read an Excel spreadsheet from COBOL?
  7. Does SET ADDRESS OF X TO Y work?
  8. What Micro Focus library routines are supported?
  9. Do I need to worry about the compile warning "Note: MYPROG.java uses unchecked or unsafe operations?"
  10. What tools are available for automated functional (regression) testing of a COBOL application?
  11. Did you know you can create temporary files in memory?
  12. Where can I obtain a copy of the ANSI 2002 COBOL standard?
  13. Is there currently a way to debug COBOL and Java source together?
  14. How do I increase the maximum Java heap size when compiling?
  15. How can I tell what changes were made in the isCOBOL latest update?
  16. How do I turn on debug trace to produce a log file?
  17. How do I determine what properties are set?
  18. Should I use JISAM or Veryant's c-treeRTG?
  19. How would I create my own CBL_ALLOC_MEM and CBL_FREE_MEM routines?
  20. What is the best way to control Microsoft Word?
  21. How can I use the F10 key in my application without it changing the keyboard focus?
  22. How do I use conditional compilation?
  23. How do I specify properties or a properties file on the command line?
  24. Where can I find more information on A$ENCRYPT and A$DECRYPT?
  25. Does isCOBOL work with Flexus COBOL sp2?
  26. How do I change the icon in the upper left corner of the Window?
  27. What is the behavior difference of STOP THREAD?
  28. Sending SMTP mail
  29. What are the defaults for the DATE-ENTRY control DISPLAY-FORMAT property and format styles?
  30. How would I create my own CBL_CHECK_FILE_EXIST routine?
  31. Is the isCOBOL 2009 SP1 release intended to deploy mainframe applications over the cloud? Or is it an integration mechanism for bringing in cloud data and apps?
  32. How do I select 11x17 paper size using WIN$PRINTER?
  33. Where can I learn more about Classpath, the Java class loader, JDK tools and utilities?
  34. What are the key technical advantages of isCOBOL?
  35. Why do I get the error message "Native call not found" and how do I fix the problem?
  36. Why do I get the error java.lang.NoClassDefFoundError: com/iscobol/rts_n/StopRunException?
  37. Can Veryant recommend a good Web site to find 3rd party JavaBeans?
  38. I still get the error : "Missing License: The license key is missing, invalid or has expired!" I can't figure out why
  39. Does isCOBOL run on Linux on System z?
  40. What compile option should I use for ICOBOL compatibility?
  41. How do I compile fixed (ANSI) format source that COPYs terminal format source or vice versa?
  42. Can isCOBOL access a DLL or .so that is in a JAR file?
  43. Can I use directory paths in CALL names?
  44. How do I configure file locations with environment variables?
  45. Is your runtime library backward compatible?
  46. What algorithm does isCOBOL use to load framework properties (runtime config variables)?
  47. How do I set iscobol.file.index.FileName with variable file name assignments?
  48. What is the easiest and/or best way to convert a legacy text-based user interface to a web front end?
  49. How can I make my isCOBOL program to be called instead of a C routine when both have the same name?
  50. Is isCOBOL backward compatible?
  51. How do I specify which file status codes I want to use?
  52. Does isCOBOL APS run on z/OS?
  53. Is there any equivalent to COPY RESOURCE?
  54. Does isCOBOL support C$REDIRECT?
  55. Why do I get the error message “java.lang.UnsatisfiedLinkError: no ### in java.library.path?
  56. What is the best way to profile an isCOBOL program?
  57. How do I write my own replacement for a C$ library routine?
  58. What should I use for USAGE HANDLE items instead of NULL?
  59. How can I avoid the "java.lang.OutOfMemoryError: PermGen space" error?
  60. Can you derive isCOBOL object classes from Java and vice versa?
  61. Is there any way to use isCOBOL with SCO 5.0.6 (JDK 1.3)?
  62. Can the file system (iscobol.file.index) be set programmatically?
  63. I've heard there is a problem passing pointers to C functions. What is it?
  64. How can I monitor a jvm started on a remote computer box?
  65. How do I get more information when I get java.lang.reflect.InvocationTargetException?
  66. Does isCOBOL support Crystal Reports or other Report Writers?
  67. How do I suppress multiple reserved words with the -rw compiler option?
  68. Why do I get the error message "java.lang.NullPointerException" ?
  69. Why do I get the error message "java.lang.ArrayIndexOutOfBoundsException" ?
  70. Can I call an RMCobol program passing parameters to it?
  71. What does mean the error NO X11 DISPLAY?
  72. How can I encode a URL String?
  73. What can I use to perform an email validation during entry-field accept?
  74. Working with sequential files on Pipes
  75. How do I resolve the error "java.lang.NoClassDefFoundError" or "java.lang.ClassNotFoundException"?
  76. Does isCOBOL support C$XML or other XML interfaces?
  77. Is there any way to direct the output from the "Print Screen" keyboard key directly to a printer?
  78. Why do I get the error "Could not load the main class" ?
  79. Did you know isCOBOL IDE allows you to easily understand how to invoke a method in a Java Class?
  80. Did you know you could set a background image from isCOBOL IDE's painter?
  81. Did you know that in a string you can replace a text with a new one with a different length by using the C$REPLACE_ALL routine?
  82. Did you know how to write custom information inside isCOBOL log file?
  83. How to programmatically set the attributes for PDFs?
  84. How can I read data correctly from a line-sequential file that has a different encoding from the one used by isCOBOL?
  85. Did you know you can encrypt the communication with the isCOBOL Server?
  86. GIT Server (Linux) - Install and Configuration
  87. Did you know these two ways of finding out the working directory in use?
  88. Activating and Check the isCOBOL License
  89. How to search by key with case insensitive on ISAM files
  90. How can I read a data written with a different encoding?
  91. How do I point my installed isCOBOL to a different Java location?
  92. May I create my own type definitions and reuse them?
  93. How can I generate QR codes from COBOL?
  94. How can I use the Call/Cancel custom HOOK program to get the start and end time of every CALLed program?
  95. How can I tell if my application is running in the WebClient environment or another environment?
  96. Can I define one or more data items based on the definition of another one?
  97. How can you wait for several threads to finish?
Article Information Additional Information
Article Number: 330
Created: 2022-06-16 8:37 AM
Rating: No Rating
 
Article Options Article Options
Print Question Print this Question
Email Question Email Question to Friend
Export to Adobe PDF Export to PDF File
Export to MS Word Export to MS Word
Bookmark Article
Subscribe to Article Subscribe to Article
 
Search Knowledge Base Search Knowledge Base



 
 

© Veryant - All Rights Reserved
Veryant and isCOBOL are trademarks or registered marks of Veryant in the United States and other countries. All other marks are the property of their respective owners.