z/OS 下 REXX 和 CLIST 的相对优点是什么？
在 TSO for z/OS 中使用 REXX 或 CLIST 的优点和缺点是什么？
我的理解是，CLIST 只是一种较旧的命令语言，但我们似乎收到了很多使用它们的新软件，尽管 REXX 现在是操作系统的标准配置。
是否有某些原因使得 CLIST 成为首选，特别是考虑到 REXX 的强大功能及其与 z/OS 的紧密集成？
What are the advantages and disadvantages of using either REXX or CLISTs in TSO for z/OS?
My understanding is that CLISTs are just an older command language but we seem to receive a lot of new software using them, even though REXX is now standard with the operating system.
Is there some reason why CLISTs are preferred, especially given the power of REXX and it's tight integration into z/OS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
以下是 IBM Inofcenter 的链接，概述了 REXX 和 CLIST
基本上，REXX 较新（大约 15 年），而 CLIST 较旧（在我之前 - 我已经从事了大约 30 年）。大型机人群似乎正在变老，许多构建 ISPF 面板的人在 REXX 可用之前就已经学会了他们的行业，所以我相信这只是一个“传统”问题（老狗，老把戏）。
有一段时间，我相信 IBM 希望淘汰 CLIST，转而使用 REXX，但与大型机的许多事情一样，在我有生之年不会发生任何事情！
我发现大多数 CLIST 都与通过 ISPF 面板管理 ISPF 对话框相关。对于此类应用程序来说，使用其中一种并没有任何优势。
我个人更喜欢 REXX，因为它本质上是一种更强大的语言，并且随 z/os 一起提供，因此它始终可用。此外，与 CLIST 相比，REXX 在 z/os 下可用于更多地址空间（例如 TSO 甚至批处理）。它也可以在 Windows 下使用（请参阅：Object REXX）。 Windows 版本基本上是 z/os 版本的超集，因此只要您保持非对象扩展并仔细管理 I/O，您就可以在 Windows 机器上运行与在大型机上相同的 exec。我构建了许多实用程序类型的函数，它们在大型机上运行起来与在 Windows 上运行一样轻松 - 几乎没有变化（除了管理文件 I/O 的几行代码）。
与 CLIST 不同，REXX 也非常有能力进行一些重要的数据处理。我听说 z/os 下 REXX 应用程序的性能与 Websphere 下运行的 Java 类似（假设 CPU 大小相同）。有时，我会在非常合理的时间内通过 REXX 例程处理数 GB 大小的数据文件。
不管怎样，我可以继续说下去……我相信，在回答你的问题时，REXX 从根本上来说是一个更好的工具，能够完成 CLIST 能做的所有事情，甚至更多。 CLIST 的流行只是因为程序员按照他们从小到大做事的方式做事，而不是学习更新的技术。
Here is a link to IBM's Inofcenter outlining the differences between REXX and CLIST
Basically, REXX is newer (about 15 years) and CLIST is older (before my time - I've been at it for about 30 years). The mainframe crowd seens to be getting older and many of the folks building ISPF pannels learned their trade before REXX was available so I believe it is just a matter of 'tradition' (old dogs, old tricks).
At one time I believe IBM wanted to retire CLIST in favour of REXX but as with so many things mainframe, sunsetting anyting is not going to happen in my lifetime!
I find the majority of CLIST is associated with managing ISPF dialogs via ISPF panels. There is no advantage in using one over the other for this type of application.
My personal preference is for REXX because it is a fundamentally more powerful language and is shipped with z/os so it is always available. Also, REXX is available in more address spaces under z/os than CLIST (eg. TSO and even batch). It is also available under Windows (see: Object REXX). The Windows version is basically a superset of the z/os version so as long as you keep to the non Object extentions and manage the I/O carefully, you can run the same exec on a windows box as on the mainframe. I have build a number of utility type functions that run with equal ease on the mainframe as on Windows - virtually unchanged (except for a couple of lines that manage file I/O).
Unlike CLIST, REXX is quite capable of doing some serious data crunching as well. I have heard that the performance of a REXX application under z/os is similar to Java running under Websphere (given the same size of CPU). On occasion, I have crunched multi-gigabyte sized datafiles through REXX routines in a very reasonable amout of time.
Anyway, I could go on and on... In answer to your question, I believe, is that REXX is fundamentally a better tool, capable of doing everyting CLIST can do and more. The prevelence of CLIST is just a matter of programmers doing things the way they grew up doing them as opposed to learing newer technologies.
z/OS 上的 REXX 的好处是，如果您需要严格的性能，您可以为其购买编译器和库，并获得接近本机的代码速度。
The nice thing about REXX on z/OS is that if you need serious performance, you can purchase the compiler and library for it and get near-native code speeds.
我没有完整的答案，但有一个想法。
我们公司仍然使用 CLIST，但我们也有 REXX。
在我看来：REXX 是更好的新语言，但在构建处理屏幕上数据列表/数组的 TSO 应用程序时，CLIST 仍然是首选。我什至不确定 REXX 处理屏幕上的列表/数组的效果如何。
我们仅将 REXX 用于较小的脚本之类的程序。
问候
西格斯特德
I dont have a complete answer but an idea.
I our company we also still use CLIST but we also have REXX.
As I see it: REXX is the new at better language but CLIST is still preferred when building TSO applications that handle lists/arrays of data that are put on the screen. I'm not even sure how well REXX is to handling list/arrays that are put on the screen.
We only use REXX to smaller script like programs.
Regards
Sigersted