Re: Time to Time DB2 Backup Faliure

Hi,

We have Networker 9.1 that deployed on a Win 2012 R2. We are schedule a DB2 full backup on every day 3 am. Past few months we are facing the backup failure in time to time. In the every time when the backup failed we got the below error.

Backing up the ‘PB_PROD’ database.

Unable to backup PB_PROD database due to backup request failure, SQLCODE : -2025, SQL2025N An I/O error occurred. Error code: “3”. Media on which this error

occurred: “VENDOR”.

NMDA backup failed.

64673:nsrdasv: Unable to backup PB_PROD database due to backup request failure, SQLCODE : -2025, SQL2025N An I/O error occurred. Error code: “3”. Media on which this error

occurred: “VENDOR”.

— Job Indications —

prdbsvr1:DB2:/PB_PROD/NODE0000: retried 1 times.”



But after we restart the NW services from next day onwards backup was run as normal. DB backup size is ~1.5 TB. We have open several SR‘s with DELL EMC NW support team. As per them in the very first time they advised to restart the NW services. As I previously said after restarting the services it was runnin fine. In the second time when we open the SR they asked to created a separate ddboost device to backup the data. That thing also we already did. Now we yesterday backup was again failed with the same error.



Is anyone can advised how to solve this issue permanently.

Related:

  • No Related Posts

IBM Cognos TM1 10.2 new Features

1656_900.jpg

IBM Cognos TM1 10.2. has a versatile application that interfaces with an IBM Cognos TM1 Server and coincides with other work area and web programs that associates with a similar server. You can utilize the Mobile application to do the accompanying errands:

Access all arranging applications from Cognos TM1 Applications.

View accommodation status for all endorsement hubs.

Communicate with solid shape sees in a network or graph design.

Change esteems on the iPad and submit back to the arrangement where the information is refreshed on the Cognos TM1 server.

One awesome element I adore is the “Change instrument for Microsoft Excel .xls documents.” I was as of late at customer where we confronted a couple of issues because of the utilization of 2007 and with this most recent update IBM Cognos TM1 10.2, you can change over Microsoft Excel 2007 or higher worksheets into OpenXML design.

Another great move up to IBM Cognos TM1 10.2 is the new highlights to Performance modeler. Presently some might be content with this, while a portion of the more established coders who adored the old method to make 3D squares, measurements and so on the physically way may not. Be that as it may, IBM has now included a couple of new things with Performance modeler, for example, Cube count, Feeder Optimization, Data stream charts, Data stream graphs, TurboIntegrator forms activated from work process activities, and then some!

IBM Cognos TM1 training

Related:

  • No Related Posts

7023392: IND$FILE File Transfer trouble-shooting tips with Reflection for the Web

Basic Trouble-Shooting:

Verify that the Host session is at a location where it can launch the Host-based IBM IND$FILE file transfer program:

The user typically needs to be located at one of two following host screen locations:

1.) At the TSO “READY” prompt logged into the MVS system but outside of ISPF

2.) At the ISPF Menu Option 6 – “ISPF Command Shell”

– the cursor must be on the line that begins with the “===>”

– if there are two “===>” prompts on the screen, then make sure the cursor is located on the top one

Note: To determine if a prompt on the Host screen will allow access to the IND$FILE command:

– At the current cursor location type the words “IND$FILE” then press the ENTER key.

– If this command gives get back a TRANS type error or information that says “IBM File Transfer Program”
than the user can access the IND$FILE program on the Host from this location.

(Depending on the Host system, the user may have to press the ENTER key a second or third time to get back to the prompt they started at)


Resolve any TRANS errors that occur during the file transfer attempt:

The IBM IND$FILE file transfer application will generate a TRANS code for specific type of errors that can be detected. There are lists of these codes available in a variety of locations on the internet including: https://www.microfocus.com/documentation/rumba/desktop951/RumbaSystemAdminGuide/GUID-44F7F207-D285-43B0-92D0-B5E641DB5CC6.html. These errors typically appear in a Reflection for the Web dialog box for easy review and must be dismissed to continue. After an error of this sort, make sure the Host session has returned to a READY prompt before attempting the next file transfer.

One of the more common TRANS errors seen in TSO is the “TRANS18 – Incorrect Option Specified” error. To resolve this error on a SEND command, in the Reflection for the Web file Transfer settings change the “Record Format” from the value of “variable” to the value of “default”.


Confirm that the naming convention for the TSO file/dataset is correct:

Each element (username, dataset, member) of a TSO dataset is limited to a maximum of 8 characters.

When in doubt, use the fully qualified name of the TSO data set surrounded by single tick marks and include any member names inside matched sets of parenthesis.

Example:

‘username.dataset(member)’


Problems with figuring out PC File Names or Host Dataset/Member Names:

Reflection for the Web 12.1 HF80, Reflection for the Web 12.2 HF40, Reflection for the Web 12.3 HF5, and later versions now fully support the ability to drag-and-drop files during an IND$FILE file transfer to and from the members of a TSO dataset. In the past, the user had to use the SEND AS and RECEIVE AS options and type in the name of either the PC or the Host file including possible PC path information and Host dataset and member information. Having to remember to type the proper format could lead to errors especially in the TSO naming conventions. If the SEND AS or RECEIVE AS is failing, try using the drag-and-drop method so that Reflection for the Web is responsible for figuring out the proper naming conventions. Also, if using drag-and-drop and having a file name issue, try using the SEND AS or RECEIVE AS methods and manually enter in the appropriate names of the files.

Advanced Trouble-Shooting:

Examine Java Console Logs with Reflection for the Web Client logging turned on

The Java Console Log can be used to view historical data about previous IND$FILE file transfer success and failures. Short of taking a full-blown communication trace, the Java Console log can be used to quickly examine previous file transfers but before the Java Console can be used, there is some configuration that must occur.

1. In the Windows Control Panel, open the Java applet and go to the Advanced Tab and check the boxes under “Debugging” to “Enable tracing” and “Enable logging”.

2. In the Reflection for the Web Administrative WebStation, go to the Settings option and select the Logging tab, and check the box for “Write client debug output to console”.

3. Launch the Windows browser and the Reflection for the Web session.

The Java Console log can be viewed from the Java Console itself or from the Windows WordPad or Notepad application by opening the file that is saved in the C:Users<username>AppDataLocalLowSunJavaDeploymentlog location. Use the log file created with the *.trace extension for information about IND$FILE transfers.

What to look for:

– Look for the strings “IND$FILE PUT” or “IND$FILE GET” to find the start of the file transfer attempt. This line will show you the Host name that was generated by Reflection for the Web and sent to the Host, as well as any file transfer options specified. A quick check of this line can tell you if the correct or appropriate command was sent to the Host

– Look for a string that contains the words “TRANS…”. This line(s) will show the results of the file transfer. A TRANS03 is success, but other errors can be listed.


Communication Trace from Reflection for the Web

When all else fails, a communication trace taken in the Reflection for the Web session (from the Help / Trace menu) with a description of what was tested can be used to examine a IND$FILE transfer failure. The Reflection for the Werb communication trace shows all the exchanges of data with the Host including the commands sent and the responses received so if any Host error messages or data has scrolled off the screen it will be captured in this trace. This step requires that the trace be sent to Micro Focus Technical Support and a Support Engineer with IND$FILE file transfer expertise be available to review the trace.

Related:

  • No Related Posts

Prevention policy for DB2

I need a solution

I see under the AIX prevention the only DB prevention policy for MySQl.  Is there a best practice or template  for DB2? We are trying to set up prevention for an AIX 7.2 server running IBM DB2. We have a policy in place for the  OS – but want one geared toward the Data Base.

0

Related:

Netwoker Client Direct Backup not Working

Hi,

We have the NW 9.1 deployed on a VM. OS is Win 2012 R2. We are expecting backup slowness on our DB client. It contains ~1.4 TB data. We are use the client direct for backup the data to DD. To investigate this issue we have rendered the daemon.raw file in the NW server and go through it. Then we are able to identified client direct backup it not happening. Pls refer the below log output.

70896 9/19/2018 4:00:50 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001)

91797 9/19/2018 4:00:50 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device ‘DWHDD1_Digital_Banking_Prod_DB’; setting up traditional save for save-set ID ‘3600907418’ (prdbsvr1:DB2:/PB_PROD/NODE0000)

71659 9/19/2018 7:44:12 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 done saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001) 1358 GB

70896 9/19/2018 7:44:15 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001)

91797 9/19/2018 7:44:15 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device ‘DWHDD1_Digital_Banking_Prod_DB’; setting up traditional save for save-set ID ‘2124525815’ (prdbsvr1:DB2:/PB_PROD/NODE0000)

Then we have check the connectivity between the client and DD vice versa. Connectivity is fine. And we are use the dedicated VLAN for the backup purpose. That means all the backup clients and DD are in the same range.

How can we solve this issue. Pls advised.

Related:

Re: DataDomain with IBMI Direct-Connection

Hardware

Switched connectivity supported by the host operating system. Please verify with Compatibility Guide.

Power 8 hardware: Direct or FC Switch connect

  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 8 drives on each port)
  • EN0A/577F- 16Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required
  • EN0B/577F- 16Gb PCIe2 “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required

Power 7 hardware: Direct or FC Switch connect

  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0 :(best practice is 4 drives on each port)
  • 5749/576B – 4Gb PCI-x “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0:(best practice is 8 drives on each port)
  • 5273/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0::(best practice is 8 drives on each port)
  • EN0A/577F- 16Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required
  • EN0B/577F- 16Gb PCIe2 “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port)

Power 6 hardware: Direct or FC Switch connect with Smart IOA

  • 5761/280D – 4Gb PCI-x HBA (best practice is 4 drives on each port)
  • 5704/5704 – 2Gb PCI-x HBA IBM i v5.4.5, v6.1.1:(best practice is 2 drives on each port) IOP 2844 & FC Switch required
  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5749/576B – 4Gb PCI-x “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 8 drives on each port)
  • 5273/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 8 drives on each port)

Power 5 hardware: NO Direct, FC switch required

  • 5761/280D – 4Gb PCI-x HBA (best practice is 4 drives on each port) IOP 2844 & FC Switch required
  • 5704/5704 – 2Gb PCI-x HBA IBM i v5.4.5, v6.1.0, v6.1.1:(best practice is 4 drives on each port) IOP 2844 & FC Switch required

The 5704 and 5761 IOAs support a maximum of 16 devices per card (IOP 2844 & FC Switch required to use on DD)

The 5774, 5749, 5735, 5273, EN0A & EN0B Smart-IOA’s (2 ports) support a maximum of 64 devices per port, and 128 per card, with a limit of 32 devices per tape library device

Software

The IBM i License for the VTL will need to be installed before starting any VTL connections.

It is recommended to set the Auto Configure System Value QAUTOCFG (Auto configure Devices) to 1 during the configuration of new tape devices. To change the system value from the command line enter the command CHGSYSVAL SYSVAL(QAUTOCFG) VALUE(‘1’). This value can be changed back after the configuration of the tape library and devices.

Tape Management Applications

Data Domain VTL for IBM i supports the following tape management applications along with the Native CL commands:

  1. IBM Backup and Recovery Media Services (BRMS) @ i5/OS, IBM i v5.4.5, v6.1, v6.1.1, v7.1, v7.2 and v7.3.0.
    1. Since BRMS is a licensed program product, the operating system release level will determine the BRMS release level, which is consistent with the OS level.
  2. Help Systems Robot/SAVE v12.13; only on i5/OS v7.2.0, v7.1.0 & v6.1.1

Help Systems Robot/SAVE v11.32; only on i5/OS v5r4m5, IBM i 6.1.0 & v6.1.1.

  1. LXI Enterprise Storage (MMS) v5.4.3; only on i5/OS v7.1.0 & v6.1.1, v6.1.0.

PTFs

To display individual PTFs level with a MF prefix type the follow command DSPPTF and press Enter. Look for “Release of base option”, this is the level of the hardware.

To display individual PTFs with a SI prefix type the follow command DSPPTF and press Enter TWICE. Look for “Release of base option”, this is the level of the software.

IBM i PTF (Software Patches) Levels

Table 129 IBM i PTF (SW patches) Levels

V5R4M5

V6.1.0

V6.1.1

V7.1.0

V7.2.0

Cumulative

12094

14197

14197

14283

14276

Hiper

203

186

186

125

18

DB2 for IBM i

33

32

32

32

3

Backup Recovery solution

57

52

52

39

5

Tech Refresh Level

9

1

Note

EMC supports legacy PTF levels up to what is listed in the table. Customers do not have to

be at the levels shown in the table to receive support.

V5R4M5

V5R4M5 requires PCI-x based HBAs with a separate IOP for Fiber Tape connectivity. The IOP based 5704 and 5761 are the only HBAs that are supported on V5R4M5 of i/OS.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended lowest PTF levels are:

SF99540 Cumulative PTF Package: Level 10117 (C0117540)

SF99539 Group HIPER: Level 129

SF99504 DB2 for IBM i: Level 26

SF99186 Backup Recovery Solutions: Level 32

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.



v6.1.0

V6R1M0 has been qualified to use the 5704 and 5761 IOAs on Power5 hardware, while Power6 hardware allows the use of either 5704/5761 or the “SmartIOA” cards, 5749 / 5774 / 5735. EMC highly recommends the use of the SmartIOA to get the best possible throughput when running Tape jobs. A SmartIOA also gives a larger number of VTL tape emulations for more processing resources. The latest Cumulative package should have all PTFs required for Old IOAs but if the SmartIOA is used the following will apply.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended Lowest PTF levels are:

Cumulative: SF99610

Release:

V6R1M0

Abstract:

Cumulative PTF package C1256610

Level:

11256

Oct 13, 2011

Group: SF99609

Release:

V6R1M0

Abstract:

Group Hiper

Level:

00110

Dec 6, 2011

Group: SF99601

Release:

V6R1M0

Abstract:

DB2 for IBM i

Level:

00021

Oct 8, 2011

Group: SF99187

Release:

V6R1M0

Abstract:

Backup Recovery Solutions

Level:

00024

Nov 30, 2011

However if the client cannot apply these levels above, then they can apply the minimal subset supplied below:

MF54179

MF53670

MF53550

MF52469

MF52324

MF52219

MF51777

MF51773

MF51356

MF50808

MF50176

MF46933

MF46409

v6.1.1

V6R1 has been qualified to use the 5704 and 5761 IOAs on Power5 hardware, while Power6 hardware allows the use of either 5704/5761 or the “SmartIOA” cards, 5749 / 5774 / 5735. Power7 hardware requires the use of the “SmartIOA” cards and V6.1.1 of the operating system.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended Lowest PTF levels are:

SF99610 Cumulative PTF Package: Level 10215 (C0215610)

SF99609 Group HIPER: Level 70

SF99601 DB2 for IBM i: Level 15

SF99187 Backup Recovery Solutions: Level 16

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.

Also, ensure the following individual PTFs are applied on V6.1.1 while using Smart IOAs:

There is no support for i6.1.1 in combination with applied PTF MF50093. If not needed do not apply!

SI36084

SI35218

SI34026

SI32538

MF50751

MF50691

MF50671

MF50587

MF49463

MF49458

MF49246

MF49234

MF47237

Review the Informational APAR for PTF requirements on the IBM website for the latest PTF requirements for Smart-IOAs:

II14355 – PTF PREREQUISITES AND SPECIFIC SUPPORT DATES FOR THE SMART-IOA (IOPless) FIBRE CHANNEL, SAS, and SCSI LVD ADAPTERS SUPPORT:

http://www-01.ibm.com/support/docview.wss?uid=nas27f65244c38e39c46862573cb0041f343



V7.1.0 , V7.2.0, V7.3.0

Fully supported with Data Domain OS 5.2 and Higher

V7.1.0, V7.2.0 & V7.3.0 has been qualified to use the “SmartIOA” cards.

Power 7 and Power 8 hardware has been qualified to use the “SmartIOA” cards listed above.

Required PTF due to IBM i OS FC failover:

PTF MF61618 for i 7.2

PTF MF61619 for i 7.3

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.

VIOS (Virtual IO Server)

Fully supported with Data Domain OS 5.2.

Virtual Input Output Server, also known as PowerVM. PowerVM is a virtualization layer

supporting the IBM i on blades and the Power6 platform at V6.1 and above. VIOS can only connect with the Data Domain System through a NPIV Switch and a 5735/577D – 8Gb PCIe “SmartIOA” card.

  • Data Domain OS v5.2 and higher supports
    • IBM VIOS versions: v2.1.x & v2.2.x
    • IBM i OS: v6.1.0, v7.1.0, v7.2.0, & V7.3.0
    • Only IOA supported: 5735/577D – 8GB PCIe “SmartIOA”



The IBM i License for the VTL will need to be installed before starting any VTL connections.

The IBM i utilizes a hardware virtualization layer commonly referred to as the Licensed Internal Code, or LIC, to provide access from the operating system to physical hardware. All peripheral equipment must emulate IBM equipment, including IBM tape libraries and devices, when presented to the operating system.

Additionally, there are no hardware drivers used by i/OS. All drivers are embedded in the LIC, or in LIC PTFs, or Program Temporary Fixes. In most cases, hardware configuration settings cannot be manually configured, as only IBM or IBM emulated equipment will be attached, requiring only fixed configuration settings.

Fiber Channel devices can be connected directly to IBM i host through an arbitrated loop (FC-AL) topology or through a switched fabric (FC-SW) topology, the DD VTL supports both switched fabric for connectivity or direct connect. The IBM i Fiber Channel host bus adapters or IOAs (Input / Output Adapters) can negotiate at 2 GB, 4GB, and 8GB speeds in a FC-SW environment without any configuration on the operating system other than plugging in the cable at the host.

While the IBM i HBAs support switched or direct connection for tape, the Data Domain VTL can also use switched connectivity or direct connect. Switched connectivity also allows access to a greater number of HBAs and increase flexibility and scalability, as well as the ability to share a single library among multiple systems.

A zone is comprised of a set of devices that access one another, in an initiator to target model. It is required that only one target and one initiator be in each VTL zone. Additional HBAs may be assigned to a VTL HBA by adding another zone. Soft zoning is recommended, in which the zone will consist of the WWPN or alias of one of the HBA ports on the Data Domain VTL, and the WWPN or alias of one of the IBM i HBA ports. Zones are then added to a zone set and activated.

4 Gb or 8 Gb switches are recommended for connectivity to IBM i. The list of IBM i qualified switches are listed in the IBM interoperability matrix.

Once the cabling of the VTL and the IBM i HBA has been completed, create appropriate tape zones with one initiator and one target: the WWPN of the VTL HBA and the WWPN of the IBM i HBA. The IBM i does not allow multiple paths to tape devices, so the zoning for each library or tape device should consist of only one initiator and one target.

Related:

7022962: Mail relay not working with SLES11 postfix

This document (7022962) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)

Situation

Customer has a SLES11 SP3 server and when they configure postfix to relay mail to another SMTP server, it fails to relay the mail message and shows an error in the /var/log/mail log file, the error is :

May 1 18:24:21 USA-US-X1015 postfix/smtpd[29037]: NOQUEUE: reject: RCPT from unknown[10.43.64.178]: 451 4.3.0 <john.smith@mycompany.com>: Temporary lookup failure; from=<john.smith@mycompany.com> to=<john.smith@mycompany.com> proto=ESMTP helo=<mycompany.com>

Resolution

It was discovered in the problem server “main.cf” file there as an invalid ip address range listed in the

“mynetworks” parameter. Of the 28 ip address ranges listed in this parameter, one was invalid, it was :
10.205.149/0/24
It should be :
10.205.149.0/24
Once this was corrected and postfix restarted, the problem went away.

Cause

Invalid ip address range in the postfix main.cf configuration file.

Additional Information

A clue to this solution was listed in the error one line above the error listed in the “Situation” section of this

technical document, it was :
postfix/smtpd[29037]: warning: bad net/mask pattern: “10.205.149/0/24”

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7021498: Using the Show Host Files File Transfer Dialog in Reflection Desktop 16, Reflection 2014, or Reflection 2011

The Show Host Files feature makes it possible to quickly retrieve a list of host file names from a 3270 IBM Host system. The host files are displayed in a tree view, and the display you see depends on the protocol selected. Reflection displays only those files that can be transferred using the currently selected transfer protocol.

Note: Show Host Files is not available if you are connected to a CICS host.

To use Show Host Files:

  1. Connect a configured terminal session using Reflection Desktop 16, Reflection 2014 or Reflection 2011, and logon to your host.
  2. In the Transfer group on the Session ribbon, click File Transfer.
  3. In the Transfer dialog box, click Setup. On the Protocol tab, select Mainframe under Protocol and select the proper system type (CMS or TSO) under Host system. Click OK.
  4. Click the Show Host Files button.

Using the Show Host Files Feature on CMS and TSO Systems

The process that Reflection uses to display a list of host files on the workstation differs between CMS and TSO systems.

CMS

On a CMS system, the Show Host Files button executes the LISTFILE command through the terminal session. The output of LISTFILE is then used to populate the Show Host Files list box with file names.

TSO

On a TSO system, the Show Host Files button executes the LISTCAT command through the terminal session. The output of the LISTCAT command is then used to populate the Show Host Files list box with file names.

Note: Some prior versions of Reflection required you to upload two Attachmate-supplied REXX execs to TSO to support the Show Host Files function. These files (WRQLDS and WRQLCAT) are no longer needed.

Troubleshooting Show Host Files Problems

If clicking the Show Host Files button does not display the host file list, follow these troubleshooting procedures in the order they are presented.

Verify Your Host Connection

Verify that you are connected to the host and that the correct system (CMS or TSO) has been selected. Follow these steps to change the system type, if necessary:

  1. On the Reflection Session ribbon, click File Transfer in the Transfer group.
  2. In the center of the Transfer dialog box, click the Setup button.
  3. On the Transfer Setup > Protocol tab, select Mainframe under Protocol and select the proper system type (CMS or TSO) under Host system. Click OK.

Verify That the Host Screen Can Accept Input

Verify that the host screen can accept and process command input. Not all host screens can accept commands. Being at the CMS or TSO command prompt is preferred, but you may also be in ISPF if you use Option 6.

Verify the CMS Command

If you are on a CMS system, logon to your host and enter the following command at the Ready; prompt:

LISTFILE

If you receive an error when attempting to run LISTFILE, contact your system administrator for assistance.

If the command runs without generating an error, contact Micro Focus Customer Support to trouble-shoot further problems with the Show Host Files functionality.

Verify the TSO Command

If you are on a TSO system, logon to your host and enter the following command at the READY prompt:

LISTCAT

If you receive an error when attempting to run LISTCAT, contact your system administrator for assistance.

If the command runs without generating an error, contact Micro Focus Customer Support to trouble-shoot further problems with the Show Host Files functionality.

Related: