- "Rexx" represents source code of MVS Rexx program.
- "Panel" is a TSO/ISPF panel source code (screen description).
- "Skeleton is a TSO/ISPF skeleton used in file tailoring process (i.e. JCL template).
| Q: What are the "Rexx", "Panels" and "Skeletons"? | |
| A:
|
| Q: How do I run these programs under my TSO user account? | |||||||||||||
|
A:
where {userid} represents your default High Level Qualifier (HLQ) of default system prefix. |
||||||||||||
| Q: I have uploaded all the necessary files, but it still won't run ! | |
|
A: make sure that the libraries that you have used to store uploaded code are in your search path, i.e. they have to be allocated to your TSO/ISPF session. To check your allocated DDNAMES and datasets that are in the search path type "TSO ISRFIND" on your command line, followed by ENTER. |
| Q: How do I add my libraries to the allocation sequence for my TSO session? | ||||||||||||||||||||||||||||
|
A: You need to modify your logon proc to include your libraries under appropriate DD name, i.e.
|
|||||||||||||||||||||||||||
| Q: Where is my logon PROC and how do I change it ? | |
|
A: If you don't know where your logon PROC is, please talk to your System Programmer. Be VERY careful when modifying your logon PROC, because you won't be able to log on again to your TSO session if you make a mistake ! |
| Q: I have changed my logon PROC and now I can not log on to my TSO account ! | |
|
A: Talk to your System Programmer and explain what you did. Next time you attempt to change your logon PROC, please have your System Programmer verify your changes BEFORE you terminate your current TSO session. |
| Q: We don't have TCP/IP connectivity to our MAINFRAME. Can we still use MAINFRAME/Web Reports ? | |
|
A: Yes. Your process will not be fully automated as you will have to manually download converted, HTML files from the MAINFRAME to your PC and then upload them onto your Web server via TCP/IP or LAN. |
| Q: Is the report published this way secure on the Internet ? | |
|
A: The report will be as secure as your Web server is. If configured properly it will be as secure as any other private network. Here you can read IBM's white paper on secure Virtual Private Networks (VPN). |
| Q: I don't want my corporate reports to be available to everybody on the Internet. How would I limit the access to the published reports ? | |
|
A: The best way to limit accessibility to your corporate data is to use Intranet vs. Internet concept. This way the network is physically separated from the outside world. If you need Internet capabilities due to geographic dispersion of clients and you still want to keep privacy of the network, your best bet would be Internet based private network. This type of network will provide you with long-distance availability and low overhead of Internet on one hand and with secure, encrypted, private Intranet-style network on the other. |
| Q: Do we need any special client software or plug-in to view out reports on the Web ? | |
|
A: No. All you need is a standard browser software, i.e. Netscape Navigator 2.0 or newer or Microsoft Internet Explorer 2.0 or newer. |
| Q: Do we need a Web server in order to view reports on our LAN ? | |
|
A: No. You can run MAINFRAME/Web Reports on the MAINFRAME side and download your HTML files straight to your LAN file server. All the clients that can access your file server on the LAN will have the ability to view the reports using their client-side browser software in the same manner as they would access the HTML being served by Web server. |
