Hi there, Our organisation is in the process of shifting from an on premise strategy to a Cloud strategy. As part of this shift, we are looking to migrate our Micro Focus estate to the Azure cloud. We currently have Microfocus Enterprise Server 2.2.1(hotfix 7) installed that allows us to operate three main environments : 1) A CICS COBOL application using VSAM and DB2 data that utilises FileShare Server 2) Multiple batch COBOL programs(that use compiler dialect Enterprise COBOL for z/OS) executed by JCL that use VSAM. QSAM and DB2 data 3) Multiple batch COBOL programs(that use compiler dialect MicroFocus) again executed by JCL that use QSAM data and utilise windows command line utilities to convert data from EBCDIC to ASCII and vice versa in order to facilitate FTP, email and print activities We are in very early talks with Micro Focus about this, but has anybody else attempted this? I'm trying to figure out what Enterprise Server product will work in the Azure cloud... can we just use the version we have now? Do we need to upgrade to Enterprise Server 3.0? Or do we need the Enterprise Server for .Net product? Are there any limitations with hosting our three main environments in the cloud? Does it depend on the Enterprise Server product? I have heard that VSAM is not supported in Azure, so a data conversion to SQL server would be required?? I've got a lot of experience with our Micro Focus estate, we started running all of the above in MFE, then SEE, now ES, however I've no real Cloud experience, so any assistance anyone can give would be greatly appreciated! Thanks Paul
↧
Forum Post: Enterprise Server in Azure?
↧
Forum Post: RE: Enterprise Server in Azure?
It depends on how you want to use Azure. If you're simply looking at Azure for IaaS - hosting Windows VMs - then you should be able to run Enterprise Server 2.2 there essentially unchanged. Network access, e.g. for your FTP connections, will require some Azure IaaS administration. Enterprise Server for .NET can run in Azure in IaaS or PaaS mode. In the latter case, ES for .NET runs as a set of worker roles that can be elastically scaled and managed by Azure, and it uses SQL Server Azure for region data and scale-out. But ES for .NET is a radically different product from native ES. It is not a drop-in replacement. Both products have their advantages and disadvantages, and they have different feature sets. While you may want to look at ES for .NET, moving to it is a significant migration.
↧
↧
Forum Post: RE: Enterprise Server in Azure?
Thanks for the information Michael, and for responding so quickly, it's much appreciated. The significant migration you mention going to .Net may not be worth it, if all we end up with is the same old system running in a new cloud environment, giving the user no perceived benefits. However the migration could involve modernization to the system that would potentially make it worth while. Yes, we've a lot to think about, but your info will be a great starting point for us in future conversations we have with Micro Focus. Thanks again Paul
↧
Wiki Page: What does ESMAC CONTROL 'Monitor 1 and 15' statistics 'average task len' show?
PROBLEM When looking in ESMAC CONTROL at 'Monitor 1 and 15' to see the statistics 'average task len', why do these not go up when there is a looping task? RESOLUTION These monitor screens contain statistics from a system point of view for the last minute or 15 minutes. The statistics are averages of latency and task duration and the number of tasks per second for completed tasks. So if a task is still in progress, as in this case, then it will not be part of those statistics (this information can be seen on active tasks on the SEPs page). For further information on individual tasks, then you will need to use HSF. Note that HSF records are only generated when tasks have completed. How can you see a runaway task; Look into Runaway Timeout/Input timeout options: Runaway Timeout is the amount of time that the region will allow the transaction to run without making a CICS, EZASOKET or MQSeries API call. The system is checked to see if any running transactions have exceeded this timeout every 10 seconds. The actual amount of time to abend a transaction may take longer. If the runaway task is looping performing CICS, EZASOCKET or MQSeries API calls then the runaway task timeout will never come into effect and one of the other timeouts such as Input Timeout (see below) should be used instead. Timeout values less than 10 seconds will not work. This is because the system only checks for runaway transactions approximately every 10 seconds. Even setting a value greater than 10 seconds does not guarantee that the transaction will be stopped after precisely that time as it will depend upon when the system check for runaway transactions after the time period has passed. The actual time it takes to timeout a runaway transaction will depend on what the transaction is doing. It will only timeout if the transaction has not issued a CICS, EZASOCKET or MQ Series API calls for the specified period. So if your transaction is in a loop where it is making new CICS calls within the period it will not time out. In addition to the runaway timeout there are two additional timeouts that can be set: 1. ID timeout - This is the amount of time a terminal session can be idle before it is disconnected. 2. Input timeout - Similar to ID Timeout except that it's the amount of time to wait for input from a terminal before terminating.
↧
Wiki Page: Installing Enterprise Server results in a Memory Fault (coredump).
PROBLEM When trying to install Enterprise Server results in a Memory Fault (coredump). RESOLUTION When doing a (gdb) file setup_ent_server_2.3_update1_redhat_x86_64 (or other versions) "/home/products/MF/setup_ent_server_2.3_update1_redhat_x86_64": not in executable format: File format not recognized This gives a clue as per Readme you need 32bit C libraries installed: The Readme file that comes with the installation shows the following is required to be able to install the product: Software Requirements Note: This product includes OpenSSL version 1.0.1p. Before installing this product, you must have the following software installed on your computer: • The pax archiving utility is required by the setup file. Pax is distributed with most UNIX/Linux systems but, if it is missing, you must install it separately. To verify pax is installed, run pax --help or pax -- version at the command line. • On Red Hat 6.x and Red Hat 7, you must have the following operating system libraries installed: glibc-*.x86_64 glibc-*.i686 libgcc-*.x86_64 libgcc-*.i686 libstdc++-*.x86_64 libstdc++-*.i686 After installing the right libraries the product installs OK.
↧
↧
Wiki Page: CASCS1015E Outbound transaction routing of transaction trans-id failed because system 'system-id' is not acquired.
Problem: CASCS1015E Outbound transaction routing of transaction trans-id failed because system 'system-id' is not acquired. Documentation references here . Resolution: If this error is encountered after a successful CRTE transaction in an MSS CICS to MSS CICS setup, then it may be caused by a) the name of the ISC listener - give it a 4-char name, something like ‘ISC1’ b) a missing ephemeral port on the ISC listener in the Originating MSS Region Example ISC definition in originating region:
↧
Wiki Page: zServer Startup Error ZCF0037E
Problem: The following error is encountered in a z/Server task after upgrading to Enterprise Developer v3.0 'ZCF0037E … Invalid parameter for z/Server: xxxxxxxxxxxx ' Resolution: Check the line of JCL in the Holder job to ensure that two commas are present at the end e.g. //TAURHOLD EXEC PGM=TAURHOLD,REGION=nnM,TIME=NOLIMIT,PARM='/&P1 ,, '
↧
Wiki Page: SQL error 19703 connecting to Oracle from PL/I
Problem: 19703 SQL error trying to connect to Oracle Database from PL/I with the following code dcl dbdbase value('xxxxx') char; dcl dbuser value('yyyyy') char; dcl dbpass value('zzzzz') char; Exec sql connect :dbdbase USER :dbuser using :dbpass; Narrative: According to the SQL standards the arguments for the Connect should be variables and not constants. The usage of 'value' causes the arguments to be defined as constants, whereas the usage of 'init' causes the arguments to be defined as variables. Resolution: Amend the code such that the variables are defined with a specific length, and initialised with ‘init’, e.g. dcl dbname char(8) init('xxxxx'); dcl dbuser char(8) init('yyyyy'); dcl dbpass char(9) init('zzzzz'); exec sql connect to :dbdbase user :dbuser using :dbpass;
↧
Wiki Page: How to force use of MFSORT64 as default when calling MFSORT (normal default is MFSORT32)
Problem How to force use of MFSORT64 as default when calling MFSORT (normal default is MFSORT32) Resolution Before running the sort command, JCL or script, run the command cobmode This will return what the "Effective Default Working Mode" is : for example the command will return "Effective Default Working Mode: 32 bit" To set this to the required mode, use the command export COBMODE=32 or export COBMODE=64 By setting the required mode, the MFSORT for that mode will be selected when MFSORT is called or run. Running MFSORT32 or MFSORT64 directly will work, instead of just running MFSORT and allowing the default cobmode to be used. Incident#3111090
↧
↧
Wiki Page: How can a file be sorted in EBCDIC order in an ASCII environment using JCL ?
Problem How can a file be sorted in EBCDIC order in an ASCII environment using JCL ? Resolution To sort a file in EBCDIC order in an ASCII environment using JCL, use the ALTSEQ CODE option/parameter. The attached zip file EBCDIC.zip, contains a sample JCL called EBCDIC.JCL, this JCL gives the results using SORT in EBCDIC order when run in an ASCII environment/region. EBCDIC.zip The ALTSEQ parameter should look like this ... ALTSEQ CODE=(30F0,31F1,32F2,33F3,34F4,35F5,36F6,37F7,38F8,39F9, 6141,6242,6343,6444,6545,6646,6747,6848,6949,6A4A, 6B4B,6C4C,6D4D,6E4E,6F4F,7050,7151,7252,7353,7454, 7555,7656,7757,7858,7959,7A5A, 4161,4262,4363,4464,4565,4666,4767,4868,4969,4A6A, 4B6B,4C6C,4D6D,4E6E,4F6F,5070,5171,5272,5373,5474, 5575,5676,5777,5878,5979,5A7A) Incident#3116169
↧
Wiki Page: If HIGH-VALUES are used in an SQL Query between Enterprise Server on UNIX and DB2 on the mainframe, the results are incorrect.
Problem If HIGH-VALUES are used in an SQL Query between Enterprise Server on UNIX and DB2 on the mainframe, the results are incorrect. If HIGH-VALUES are replaced by 9's, the SQL Query will return the correct results. What causes incorrect results and how can this be avoided? This problem was/is only visible in product version 2.3 Update 2 hot fix 8 and previous versions. Resolution The problem is caused by character conversion of HIGH-VALUES (x'FF') between UNIX and the local DB2LUW. The character being supplied to the mainframe DB2 system is not x'FF' so the results will be correct for the value supplied, which will be no rows returned. The solution is to have a correct codepage conversion in place on the UNIX platform. To use this on the UNIX machine.. 1. Download CS9000.cbl and codeset31.cpy and codeset34.cpy contained in the attached file ( DB2HighValues.zip ) 3617.DB2HighValues.zip - Copybook codeset31.cpy is for Windows 31 MFCODESET (English) - Copybook codeset34.cpy is for Windows 34 MFCODESET (Spanish) 2. Rename required copybook to codeset.cpy 3. Compile CS9000.cbl with >cob –z CS9000.cbl 4. Move the CS9000.so to ANY directory of your choice. Making sure the directory is included in the LD_LIBRARY_PATH. 5. export MFCODESET=9000 6. export LANG=en_US.iso88591 - NOTE - To use this MFCODESET in an Enterprise Server region.. a) stop your ES Region b) Update your server /region configuration settings as follows: - Enterprise Server Administration Panel > RegionName > Edit - Server tab > Properties tab > General tab > Configuration Information panel - Enter the Environment variables as follows: [ES-Environment] MFCODESET=31 LANG=en-US.iso8859-1 c) restart your ES Region 6. Run application and this will pick up the new codepage and correct the issue This special MFCODESET is now included in the product delivery for version 2.3 Update 2 hot fix 9 (onwards) and version 3.0 (onwards) Incident#3111843
↧
Wiki Page: How to echo console messages to /var/log/messages
Problem How to echo console messages to /var/log/messages Resolution Each ES region has its own Console Log. Depending on how regions have been configured, there may be more than one Console Log that needs to be monitored. So in order to facilitate monitoring, optionally on Linux and UNIX systems, a region can also be configured to send its messages to the /var/log/messages file. From there the file can be monitored for the key messages. This can either be configured when ES is installed or by setting the following in $COBDIR/etc/cas/cas.cfg file: USESYSCON=Y' Incident#3116887
↧
Wiki Page: MN1003E Failed to get license for MTO: Error[18]: No license code is available for feature MTODevelopment on host 127.0 : How can this message be removed from the MFDS log?
Problem MN1003E Failed to get license for MTO: Error[18]: No license code is available for feature MTODevelopment on host 127.0 : How can this message be removed from the MFDS log? Resolution The message is basically a warning to advise that there is no MTO license installed The message will continue to be reported/displayed until one of the following happens... 1. An MTO license is installed. If CICS is not used in ES this seems unnecessary. 2. Set the MF_MFDS_DISABLE_LICENSING environment variable and this will stop the license check. The license check in MFDS is not used to enforce feature functionality, but simply to not display CICS configuration screens and security features that do not work for non-SOA features. 3. To do this, set the variable in the MFDS script in the /bin directory. Change the script to include a new statement after the statement export SHLIB_PATH The amended part of the MFDS script would look like this. LD_LIBRARY_PATH=$COBDIR/lib:${LD_LIBRARY_PATH-/usr/lib} export LD_LIBRARY_PATH LIBPATH=$COBDIR/lib:${LIBPATH-/usr/lib} export LIBPATH SHLIB_PATH=$COBDIR/lib:${SHLIB_PATH-/usr/lib} export SHLIB_PATH export MF_MFDS_DISABLE_LICENSING=Y 4. Stop and restart MFDS to activate this functionality. Incident#3116985
↧
↧
Wiki Page: When running DB2 programs in Enterprise Server, how can an SQL -818 error be resolved ?
Problem When running DB2 programs in Enterprise Server, how can an SQL -818 error be resolved ? Resolution When compiling the program, make sure the DB2 compiler directives BINDDIR and BIND are defined. BINDDIR must be set to the full path of the file that will be generated. BIND will generate a file in directory pointed to by BINDDIR. After the compilation is completed and the file has been generated, a manual BIND against DB2 must be done before the program can be used, and the SQL -808 or -818 avoided. Please see IBM documentation on how to use BIND from DB2 command prompt. Incident# 3112993
↧
Forum Post: How to launch mfds automatically as a Linux service
I have Linux SUSE 11 SP3 with Cobol Server 2.2. When restart the server i need to change to $COBDIR/bin and execute mfds. I tried launch as a service in /etc/init.d activate for level 3 and 5 of boot. It don't work. I tried launch as a process in crontab (at reboot). It don't work. Check /var/log/boot.msg ... mfds start Running /etc/init.d/rc5.d/S01mfds (start)... Done /etc/init.d/rc5.d/S01mfds 'mfds start' exits with status 0 ... but mfds don´t work (the port 86 web administrator show not found and the process mfds is not in the list of active process). What need to start mfds automatically at reboot? Please send me any suggestions. Thanks in advance, Enrique Vera.
↧
Forum Post: RE: How to launch mfds automatically as a Linux service
Probably you're missing something necessary in the environment, or starting MFDS under a non-privileged account. (MFDS needs to run as root in order to bind to port 86, which is a reserved port on UNIX/Linux systems.) If you provided the contents of S01mfds, we might be able to guess what the problem is.
↧
Forum Post: RE: How to launch mfds automatically as a Linux service
Michael, The contents of S01mfds is: #!/bin/bash # Author: your name here # # /etc/init.d/mfds # ### BEGIN INIT INFO # Provides: mfds # Required-Start: $null # Should-Start: $null # Required-Stop: $null # Should-Stop: $null # Default-Start: 3 4 5 # Default-Stop: 3 4 5 # Short-Description: Microfocus Directory Services. # Description: MFDS for Web Services Cobol. ### END INIT INFO . /etc/rc.status rc_reset COBDIR=/opt/microfocus/VisualCOBOL PATH=/opt/microfocus/VisualCOBOL/bin:/sbin:/usr/sbin:/usr/local/sbin:/root/bi n:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/li b/mit/bin:/usr/lib/mit/sbin case "$1" in start) # use colour for ease of spotting echo -e "\E[36mRunning $0 (start)...\E[0m"; nohup /opt/microfocus/VisualCOBOL/bin/mfds & echo -e "\E[36mDone $0 \E[0m"; ;; stop) echo -e "\E[36mRunning $0 (stop)...\E[0m"; /opt/microfocus/VisualCOBOL/bin/mfds -s 2 echo -e "\E[36mDone $0 \E[0m"; ;; restart) $0 stop $0 start rc_status ;; *) echo "Usage $0 (start|stop|restart)" exit 1; ;; esac rc_exit #
↧
↧
Forum Post: RE: How to launch mfds automatically as a Linux service
Well, for one thing, you're not exporting COBDIR. (PATH should already be exported, though it wouldn't hurt to export it again.) Nor are you setting LD_LIBRARY_PATH, though $COBDIR/bin/mfds is actually a shell script which exports it for you. I'm also wondering why you're including things like /usr/bin/X11 and /usr/games in PATH. That looks like you copied some other start/stop script rather than creating one specific to your needs. And you're not capturing any output from the mfds script or the mfds32 process it will eventually execute. And you made this an S01* script, which means it will run early in the runlevel. Possibly too early. Why are you trying to run it at that point? (And "Micro Focus" is two words.) I suggest renaming the script to something more reasonable like S95mfds, and rewriting it along these lines: #!/bin/bash # Author: your name here # # /etc/init.d/mfds # ### BEGIN INIT INFO # Provides: mfds # Required-Start: $null # Should-Start: $null # Required-Stop: $null # Should-Stop: $null # Default-Start: 3 4 5 # Default-Stop: 3 4 5 # Short-Description: Micro Focus Directory Services. # Description: MFDS for Web Services Cobol. ### END INIT INFO . /etc/rc.status rc_reset export COBDIR=/opt/microfocus/VisualCOBOL export PATH=$COBDIR/bin:$PATH:/bin # log file LOGDIR=/var/mfcobol/logs LOGFILE=$LOGDIR/S95mfds.log mkdir -p $LOGDIR echo "$(date): $1" >>| $LOGFILE case "$1" in start) # use colour for ease of spotting echo -e "\E[36mRunning $0 (start)...\E[0m"; nohup $COBDIR/bin/mfds >> $LOGFILE 2>&1 & echo -e "\E[36mDone $0 \E[0m"; ;; stop) echo -e "\E[36mRunning $0 (stop)...\E[0m"; $COBDIR/bin/mfds -s 2 >> $LOGFILE 2>&1 echo -e "\E[36mDone $0 \E[0m"; ;; restart) $0 stop $0 start rc_status ;; *) echo "Usage $0 (start|stop|restart)" exit 1; ;; esac rc_exit # Untested, but give it a try. If it doesn't work, post the contents of /var/mfcobol/logs/S95mfds.log.
↧
Forum Post: RE: How to launch mfds automatically as a Linux service
Michael, My previous script is "under construction", i copied the PATH (and other environment variables) and use for trial-and-error approach because lack of documentation about this topic (launch mfds as a Linux service). The use of S01 is because initially use S95 without sucess, so change it run early for test conflict with other service. The good news: the script run fine, with a minor change: the line echo "$(date): $1" >>| $LOGFILE don't need the |, so the correct line is: echo "$(date): $1" >> $LOGFILE Thanks so much, Enrique.
↧
Forum Post: Is Enterprise Analyzer compatible with other mainframe/OS then IBM mainframe and z/OS?
Hi, I saw in Enterprise Analyzer that it mainly support IBM z/OS environment. Is there anyone know that EA supports other mainframe migration. Thanks in advance LinhPham
↧