Microfocus Cobol 安装手册
Peoplesoft系统安装
深入浅出Peoplesoft安装目录一、安装前奏安装前需要准备安装介质，介质一般有两种方式获取，1、被实施方公司在购买产品的时候会购买软件；2、从Oracle官方网站下载。
本文档第二部分会讲解下载软件列表(V开头的都为产品编号，这些产品编号对应edelivery的编号)二、安装介质下载 Oracle Edelivery SoftWareRedhat Enterpirse Linux 网上自行搜索下载Oracle DataBase 11gR2除以上软件外，其他软件都需要从edelivery中下载。
Edelivery打开比较慢，建议如果要下载在本地使用goagent（google的翻墙利器）做代理。
Goagent详细配置。
edelivery支持迅雷下载。
1.进入edlivery2.Sign In/ Register 点击按钮进入登陆页面。
输入正确的Oracle用户名和密码即可进入3.选择两个复选框后，点击continue进入网站4.按照上图选择ProductPack 和Platform 。
点击GO 。
拉倒最下面选择853 ，点击continue进入下载页面5.在下载页面可以下载到以下软件6.重复第一步选择每一个产品进入下载页面可以下载到7.重复第一步进入下载界面可以下载以下两个软件8.到Oracle官方下载JDK7软件都准备齐全就可以安装了.三、安装步骤1.安装步骤中用的图片从其他文档摘录过来，有些不显示和此版本不同，但是类似，只要类似就表示安装没有问题.安装介质解压缩的时候有重名的，所以每一个安装介质尽量子一个单独的目录避免出现解压缩问题.2.操作系统linux安装，略过，网络资料很多.3.Oracle安装略过，参照官方安装文档安装即可，Oracle安装的时候选择仅安装软件。
4.首先将下载的介质统一传到Linux服务器上，如:/setup目录下面5.规划安装目录，因为是开发环境所以本文档的安装目录为6.新增psoft用户$useradd -g psoft -G dba psoft$passwd psoft注: 输入密码后psoft用户建立完成，由于psoft要连接oracle，所以直接把dba 的权限付给psoft。
COBOL语言基础教程
cobol语言基础培训教程2009年04月23日| 5:23 下午分类:大型机｜Mainframe| 标签:cobol 数据类型、COBOL 程序举例、cobol入门、cobol教程、cobol语言、大型机培训|CHAPTER 1 COBOL 概述COBOL 就是mon Business Oriented Language 得缩写。
它不仅就是商业数据处理得理想语言,而且广泛用于数据管理领域,因此COBOL 语言也被称为”用于管理得语言”。
一。
COBOL 语言得特点最适于数据处理领域:算数计算量少而逻辑处理量多,输入输出量大,数据间存在着一定得逻辑关系,大量得分类排序;COBOL比较接近英语,容易懂;通用性强,易移植,COBOL结构严谨,层次分明。
二。
COBOL得组成部分:1。
标识部(IDENTIFICATION DIVISION):用于标识程序名。
2。
环境部(ENVIRONMENT DIVISION):用于说明程序运行得环境。
3。
数据部(DATA DIVISION):用于说明程序中涉及得所有数据。
4。
过程部(PROCEDURE DIVISION):就是程序得核心部分,它决定计算机应进行什么操作。
三。
最简单得COBOL 程序举例:COL 1 —6 7 8 12—72 73—80 IDENTIFICATION DIVISION。
PROGRAM-ID。
PSAMPLE1。
ENVIRONMENT DIVISION。
DATA DIVISION。
PROCEURE DIVISION。
DISPLAY ’THIS IS A COBOL PROGRAM、’STOP RUN。
四。
COBOL 源程序得书写格式:第1 至 6 列为”标号区”。
第7列为”续行标志区”第8至此11列,称为”A区”。
程序中有些内容如部头,节头,段头,层号01,层号77 及文件描述符FD等应从A区开始写。
第12至此72列,称为”B区”。
写程序中得正文部分。
Fortify SCA 源代码应用安全测试工具 快速入门手册说明书
Fortify SCA源代码应用安全测试工具快速入门手册文档版本：v1.0发布日期：2022-11深圳市稳安技术有限公司*************************Fortify SCA源代码应用安全测试工具快速入门手册Fortify SCA（Static Code Analyzer）是Micro Focus公司旗下的一款静态应用程序安全性测试(SAST) 产品，可供开发团队和安全专家分析源代码，检测安全漏洞，帮助开发人员更快更轻松地识别问题并排定问题优先级，然后加以解决。
Fortify SCA支持27种编程语言：ABAP/BSP、Apex，、C/C++、C#、Classic ASP、COBOL、ColdFusion、CFML、Flex/ActionScript、Java、JavaScript、JSP、Objective C、PL/SQL、PHP、Python、T-SQL、、VBScript、VB6、XML/HTML、Ruby、Swift、Scala 、Kotlin 、Go，能够检测超过1051个漏洞类别，涵盖一百多万个独立的API。
一、安装Fortify SCA源代码应用安全测试工具1、创建华为云服务器ECS1.1、主机配置建议：1.2、操作系统支持：1.3、网络配置安全组规则配置要求：1.3.1、Linux系统：22端口(SSH登录管理)1.3.2、Windows系统：3389端口(Windows RDP)1.4、安装操作系统通过VNC或CloudShell远程登录平台服务器，根据需求选用合适的镜像安装操作系统。
1.5、代码编译环境准备以下几种语言扫描需要准备相应的编译环境，代码需要在可通过编译的情况下扫描：a)C#，，b)C/C++ on Windows or Linuxc)iPhone App用户需要根据代码安装相应的编译环境，并确保需要扫描的代码能够通过编译。
2、安装Fortify SCA2.1、上传安装包完成产品购买后，根据扫描主机的操作系统，从MicroFocus下载平台下载对应的安装文件压缩包，然后解压出安装文件上传至云服务器。
第五章 莫迪康MICRO PLC编程器——MODSOFT LITE的使用
第二节Modicon Micro PLC的I/O扩展技术
一、采用A120模板进行I/O扩展
（1）PLC无论处于何种工作方式（母、子、单机运行），均可进行A120扩展
（2）PLC进行A120扩展时，本身被配置为机架1，A120的I/O机架被配置为2～4
2DAX～5DAX——2～5楼下召唤登记指示显示
YX——电梯正在运行显示
7段数码管显示轿厢所在层楼位置
a g d
0 0 1（1层）
0 1 0（2层）
0 1 1（3层）
1 0 0（4层）
1 0 1（5层）
二、开关量I/O点的参考号分配
说明：
1.根据控制要求，应有开关量输入点：23；开关量输出点：28，现1台Modicon Micro 61200PLC为16I/12O，用2台PLC可有32I/24O，因此，将7段数码管的十进制显示改为二进制显示，只用7段中的3段a、g、d，如图所示。这样，只需两台PLC即可实现控制。
·控制功能
1.召唤登记（响应）及清除功能
召唤登记：轿厢外层楼上的乘客按钮“上召唤或下召唤”，一旦响应，即予以登记
清除召唤：（1）消防方式
（2）轿厢到达召唤楼层
2.指令登记（响应）及清除功能
指令登记：轿厢内乘客按指令按钮（消防时若未到过底楼并开过门，则不允许指令登记）
指令清除：（1）到达指令楼层
（2）消防时未到过底开过门
一、电梯的工作方式
1.有司机方式——手动控制方式上、下客时间的长短
（本例中，设10003=“1”）上、下行的起动
中间是否响应召唤（或直驶）
kalilinux学习笔记（四）：网络端口大全介绍
kalilinux学习笔记（四）：⽹络端⼝⼤全介绍端⼝⼤全介绍2端⼝：管理实⽤程序3端⼝：压缩进程5端⼝：远程作业登录7端⼝：回显9端⼝：丢弃11端⼝：在线⽤户13端⼝：时间17端⼝：每⽇引⽤18端⼝：消息发送协议19端⼝：字符发⽣器20端⼝：FTP⽂件传输协议(默认数据⼝)21端⼝：FTP⽂件传输协议(控制)22端⼝：SSH远程登录协议23端⼝：telnet(终端仿真协议),⽊马Tiny Telnet Server开放此端⼝24端⼝：预留给个⼈⽤邮件系统25端⼝：SMTP服务器所开放的端⼝，⽤于发送邮件27端⼝：NSW ⽤户系统 FE29端⼝：MSG ICP31端⼝：MSG验证,⽊马Master Paradise、HackersParadise开放此端⼝33端⼝：显⽰⽀持协议35端⼝：预留给个⼈打印机服务37端⼝：时间38端⼝：路由访问协议39端⼝：资源定位协议41端⼝：图形42端⼝：主机名服务43端⼝：who is服务44端⼝：MPM(消息处理模块)标志协议45端⼝：消息处理模块46端⼝：消息处理模块(默认发送⼝)47端⼝：NI FTP48端⼝：数码⾳频后台服务49端⼝：TACACS登录主机协议50端⼝：远程邮件检查协议51端⼝：IMP(接⼝信息处理机)逻辑地址维护53端⼝：dns域名服务器54端⼝：施乐⽹络服务系统票据交换55端⼝：ISI图形语⾔56端⼝：施乐⽹络服务系统验证57端⼝：预留个⼈⽤终端访问58端⼝：施乐⽹络服务系统邮件59端⼝：预留个⼈⽂件服务60端⼝：未定义61端⼝：NI邮件62端⼝：异步通讯适配器服务63端⼝：whois++64端⼝：通讯接⼝65端⼝：TACACS数据库服务66端⼝：Oracle SQL*NET67端⼝：引导程序协议服务端68端⼝：引导程序协议客户端69端⼝：⼩型⽂件传输协议70端⼝：信息检索协议71端⼝：远程作业服务72端⼝：远程作业服务73端⼝：远程作业服务74端⼝：远程作业服务75端⼝：预留给个⼈拨出服务76端⼝：分布式外部对象存储77端⼝：预留给个⼈远程作业输⼊服务78端⼝：修正TCP79端⼝：查询远程主机在线⽤户等信息80端⼝：http,⽤于⽹页浏览,⽊马Executor开放此端⼝81端⼝：HOST2名称服务82端⼝：传输实⽤程序83端⼝：模块化智能终端ML设备84端⼝：公⽤追踪设备85端⼝：模块化智能终端ML设备86端⼝：Micro Focus Cobol编程语⾔87端⼝：预留给个⼈终端连接88端⼝：Kerberros安全认证系统89端⼝：SU/MIT telnet(终端仿真⽹关)90端⼝：DNSIX 安全属性标记图92端⼝：⽹络打印协议93端⼝：设备控制协议94端⼝：Tivoli对象调度96端⼝：DIXIE协议规范97端⼝：快速远程虚拟⽂件协议98端⼝：TAC新闻协议99端⼝：后门程序ncx99开放此端⼝100端⼝：未知⽤途101端⼝：NIC 主机名称服务102端⼝：消息传输代理103端⼝：Genesis 点对点传输⽹络105端⼝：信箱名称服务106端⼝：3COM-TSMUX开放端⼝107端⼝：远程Telnet服务108端⼝：SNA ⽹关访问服务109端⼝：POP2服务器开放此端⼝,⽤于接收邮件110端⼝：POP3服务器开放此端⼝,⽤于接收邮件111端⼝：SUN公司的RPC服务所有端⼝112端⼝：McIDAS 数据传输协议113端⼝：认证服务，⽤于鉴别TCP连接的⽤户114端⼝：⾳频新闻多点服务115端⼝：简单⽂件传输服务116端⼝：ANSA REX 通知117端⼝：UUCP 路径服务118端⼝：SQL 服务119端⼝：NEWS新闻组传输协议，承载USENET通信121端⼝：⽊马BO jammerkillahV开放端⼝122端⼝：SMAKY⽹络123端⼝：⽹络时间协议，蠕⾍病毒会利⽤，⼀般关闭128端⼝：GSS X许可认证129端⼝：密码⽣成器协议130端⼝：Cisco软件开放端⼝131端⼝：Cisco软件开放端⼝132端⼝：Cisco软件开放端⼝133端⼝：统计服务134端⼝：INGRES-⽹络服务135端⼝：DCOM服务，冲击波病毒利⽤，不能关闭136端⼝：命名系统138端⼝：NETBIOS协议应⽤，为共享开放139端⼝：NETBIOS协议应⽤，为共享开放140端⼝：EMFIS数据服务141端⼝：EMFIS控制服务143端⼝：Interim邮件访问协议144端⼝：UMA软件开放端⼝145端⼝：UAAC协议149端⼝：AED 512仿真服务150端⼝：SQL(结构化查询语⾔)-⽹络152端⼝：后台⽂件传输协议156端⼝：SQL(结构化查询语⾔)服务158端⼝：PC邮件服务器159端⼝：NSS-路由160端⼝：SGMP-陷阱161端⼝：简单⽹络管理协议162端⼝：SNMP陷阱163端⼝：CMIP/TCP 管理164端⼝：CMIP/TCP 代理166端⼝：Sirius系统169端⼝：发送170端⼝：⽹络附⾔177端⼝：x显⽰管理控制协议，⼊侵者通过它访问X-windows操作台178端⼝：NextStep Window 服务179端⼝：边界⽹关协议180端⼝：图表181端⼝：统⼀184端⼝：OC服务器185端⼝：远程-KIS186端⼝：KIS 协议187端⼝：应⽤通信接⼝189端⼝：队列⽂件传输190端⼝：⽹关进⼊控制协议191端⼝：Prospero ⽬录服务192端⼝：OSU ⽹络监视系统193端⼝：Spider 远程控制协议194端⼝：多线交谈协议197端⼝：⽬录地址服务198端⼝：⽬录地址服务监视器201端⼝：AppleTalk(Mac机所⽤的⽹络协议)路由保证202端⼝：AppleTalk(Mac机所⽤的⽹络协议)Name Binding 203端⼝：AppleTalk(Mac机所⽤的⽹络协议)未⽤端⼝204端⼝：AppleTalk(Mac机所⽤的⽹络协议)回显205端⼝：AppleTalk(Mac机所⽤的⽹络协议)未⽤端⼝206端⼝：AppleTalk(Mac机所⽤的⽹络协议)区信息207端⼝：AppleTalk(Mac机所⽤的⽹络协议)未⽤端⼝208端⼝：AppleTalk(Mac机所⽤的⽹络协议)未⽤端⼝209端⼝：快速邮件传输协议210端⼝：ANSI(美国国家标准协会)Z39.50211端⼝：Texas Instruments 914C/G终端213端⼝：IPX(以太⽹所⽤的协议)218端⼝：Netix消息记录协议219端⼝：Unisys ARPs220端⼝：交互邮件访问协议 v3223端⼝：证书分发中⼼224端⼝：masq拨号器241端⼝：预留端⼝ (224-241)245端⼝：链接246端⼝：显⽰系统协议257端⼝：安全电⼦交易系统258端⼝：Yak Winsock 个⼈聊天259端⼝：有效短程遥控260端⼝：开放端⼝261端⼝：IIOP 基于TLS/SSL的命名服务266端⼝：SCSI(⼩型计算机系统接⼝)on ST267端⼝：Tobit David服务层268端⼝：Tobit David复制281端⼝：个⼈连结282端⼝：Cable端⼝A/X286端⼝：FXP通信308端⼝：Novastor备份313端⼝：Magenta逻辑318端⼝：PKIX时间标记333端⼝：Texar安全端⼝344端⼝：Prospero数据存取协议345端⼝：Perf分析⼯作台346端⼝：Zebra服务器348端⼝：Cabletron管理协议358端⼝：Shrink可上⽹家电协议359端⼝：⽹络安全风险管理协议362端⼝：SRS发送363端⼝：RSVP隧道372端⼝：列表处理373端⼝：Legend公司374端⼝：Legend公司376端⼝：AmigaEnvoy⽹络查询协议377端⼝：NEC公司378端⼝：NEC公司379端⼝：TIA/EIA/IS-99调制解调器客户端380端⼝：TIA/EIA/IS-99调制解调器服务器381端⼝：hp(惠普)性能数据收集器382端⼝：hp(惠普)性能数据控制节点383端⼝：hp(惠普)性能数据警报管理384端⼝：远程⽹络服务器系统385端⼝：IBM应⽤程序386端⼝：ASA信息路由器定义⽂件.387端⼝：Appletalk更新路由.389端⼝：轻型⽬录访问协议395端⼝：⽹络监视控制协议396端⼝：Novell(美国Novell公司)Netware(Novell公司出的⽹络操作系统)over IP 400端⼝：⼯作站解决⽅案401端⼝：持续电源402端⼝：Genie协议406端⼝：交互式邮件⽀持协议408端⼝：Prospero资源管理程序409端⼝：Prospero资源节点管理.410端⼝：DEC(数据设备公司)远程调试协议411端⼝：远程MT协议412端⼝：陷阱协定端⼝413端⼝：存储管理服务协议414端⼝：信息查询415端⼝：B⽹络423端⼝：IBM操作计划和控制开端424端⼝：IBM操作计划和控制追踪425端⼝：智能计算机辅助设计434端⼝：移动ip代理435端⼝：移动ip管理443端⼝：基于TLS/SSL的⽹页浏览端⼝，能提供加密和通过安全端⼝传输的另⼀种HTTP 444端⼝：简单⽹络内存分页协议445端⼝：Microsoft-DS，为共享开放，震荡波病毒利⽤，⼀般应关闭446端⼝：DDM-远程关系数据库访问447端⼝：DDM-分布式⽂件管理448端⼝：DDM-使⽤安全访问远程数据库456端⼝：⽊马HACKERS PARADISE开放此端⼝458端⼝：apple quick time软件开放端⼝459端⼝：ampr-rcmd命令464端⼝：k密码服务469端⼝：⼴播控制协议470端⼝：scx-代理472端⼝：ljk-登陆481端⼝：Ph服务487端⼝：简单异步⽂件传输489端⼝：nest-协议491端⼝：go-登陆499端⼝：ISO ILL协议500端⼝：Internet密钥交换，Lsass开放端⼝，不能关闭509端⼝：陷阱510端⼝：FirstClass协议512端⼝：远程进程执⾏513端⼝：远程登陆514端⼝：cmd命令515端⼝：spooler516端⼝：可视化数据518端⼝：交谈519端⼝：unix时间520端⼝：扩展⽂件名称服务器525端⼝：时间服务526端⼝：新⽇期529端⼝：在线聊天系统服务530端⼝：远程过程调⽤531端⼝：聊天532端⼝：读新闻533端⼝：紧急⼴播端⼝537端⼝：⽹络流媒体协议542端⼝：商业543端⼝：Kerberos(软件)v4/v5544端⼝：krcmd命令546端⼝：DHCPv6 客户端547端⼝：DHCPv6 服务器552端⼝：设备共享554端⼝：Real Time Stream控制协议555端⼝：⽊马PhAse1.0、Stealth Spy、IniKiller开放此端⼝556端⼝：远距离⽂件服务器563端⼝：基于TLS/SSL的⽹络新闻传输协议564端⼝：plan 9⽂件服务565端⼝：whoami查询566端⼝：streettalk567端⼝：banyan-rpc(远程过程调⽤)568端⼝：DPA成员资格569端⼝：MSN成员资格570端⼝：demon(调试监督程序)571端⼝：udemon(调试监督程序)572端⼝：声纳573端⼝：banyan-贵宾574端⼝：FTP软件代理系统581端⼝：Bundle Discovery 协议582端⼝：SCC安全583端⼝：Philips视频会议584端⼝：密钥服务器585端⼝：IMAP4+SSL (Use 993 instead)586端⼝：密码更改587端⼝：申请589端⼝：Eye连结595端⼝：CAB协议597端⼝：PTC名称服务598端⼝：SCO⽹络服务器管理3599端⼝：Aeolon Core协议600端⼝：Sun IPC(进程间通讯)服务器601端⼝：可靠系统登陆服务604端⼝：通道606端⼝：Cray统⼀资源管理609端⼝：npmp-陷阱610端⼝：npmp-本地611端⼝：npmp-gui( 图形⽤户界⾯)612端⼝：HMMP指引613端⼝：HMMP操作614端⼝：SSL(加密套接字协议层)shell(壳)615端⼝：Internet配置管理616端⼝：SCO(Unix系统)系统管理服务器617端⼝：SCO桌⾯管理服务器619端⼝：Compaq(康柏公司)EVM620端⼝：SCO服务器管理623端⼝：ASF远程管理控制协议624端⼝：Crypto管理631端⼝：IPP (Internet打印协议)633端⼝：服务更新(Sterling软件)637端⼝：局域⽹服务器641端⼝：repcmd命令647端⼝：DHCP(动态主机配置协议)Failover648端⼝：注册登记协议(RRP)649端⼝：Cadview-3d软件协议666端⼝：⽊马Attack FTP、Satanz Backdoor开放此端⼝808端⼝：ccproxy http/gopher/ftp (over http)协议1001端⼝：⽊马Silencer，WebEx开放端⼝1011端⼝：⽊马Doly开放端⼝1024端⼝：动态端⼝的开始,⽊马yai开放端⼝1025端⼝：inetinfo.exe(互联⽹信息服务)⽊马netspy开放端⼝1026端⼝：inetinfo.exe(互联⽹信息服务)1027端⼝：应⽤层⽹关服务1030端⼝：应⽤层⽹关服务1031端⼝：BBN IAD1033端⼝：本地⽹络信息端⼝1034端⼝：同步通知1036端⼝：安全部分传输协议1070端⼝：⽊马Psyber Stream，Streaming Audio开放端⼝1071端⼝：⽹络服务开放端⼝1074端⼝：⽹络服务开放端⼝1080端⼝：Socks这⼀协议以通道⽅式穿过防⽕墙，允许防⽕墙后⾯的⼈通过⼀个IP地址访问INTERNET 1110端⼝：卡巴斯基反病毒软件开放此端⼝1203端⼝：许可证⽣效端⼝1204端⼝：登陆请求监听端⼝1206端⼝：Anthony数据端⼝1222端⼝：SNI R&D⽹络端⼝1233端⼝：普遍的附录服务器端⼝1234端⼝：⽊马SubSeven2.0、Ultors Trojan开放此端⼝1243端⼝：⽊马SubSeven1.0/1.9开放此端⼝1245端⼝：⽊马Vodoo，GabanBus，NetBus，Vodoo开放此端⼝1273端⼝：EMC-⽹关端⼝1289端⼝：JWalk服务器端⼝1290端⼝：WinJa服务器端⼝1333端⼝：密码策略(⽹络服务)(svchost.exe)1334端⼝：⽹络服务(svchost.exe)1335端⼝：数字公正协议1336端⼝：即时聊天协议(svchost.exe)1349端⼝：注册⽹络协议端⼝1350端⼝：注册⽹络协议端⼝1371端⼝：富⼠通配置协议端⼝1372端⼝：富⼠通配置协议端⼝1374端⼝：EPI软件系统端⼝1376端⼝：IBM个⼈-个⼈软件端⼝1377端⼝：Cichlid许可证管理端⼝1378端⼝：Elan许可证管理端⼝1380端⼝：Telesis⽹络许可证管理端⼝1381端⼝：苹果⽹络许可证管理端⼝1386端⼝：CheckSum 许可证管理端⼝1387端⼝：系统开放端⼝(rundll32.exe)1388端⼝：数据库⾼速缓存端⼝1389端⼝：⽂档管理端⼝1390端⼝：存储控制器端⼝1391端⼝：存储器存取服务器端⼝1392端⼝：打印管理端⼝1393端⼝：⽹络登陆服务器端⼝1394端⼝：⽹络登陆客户端端⼝1395端⼝：PC⼯作站管理软件端⼝1396端⼝：DVL活跃邮件端⼝1397端⼝：⾳频活跃邮件端⼝1398端⼝：视频活跃邮件端⼝1433端⼝：Microsoft的SQL服务开放端⼝1434端⼝：Microsoft的SQL服务监视端⼝1492端⼝：⽊马FTP99CMP开放此端⼝1509端⼝：⽊马Psyber Streaming Server开放此端⼝1512端⼝：Microsoft Windows⽹络名称服务1524端⼝：许多攻击脚本安装⼀个后门SHELL于这个端⼝1600端⼝：⽊马Shivka-Burka开放此端⼝1645端⼝：远程认证拨号⽤户服务1701端⼝：第2层隧道协议1731端⼝：NetMeeting⾳频调⽤控制1801端⼝：Microsoft消息队列服务器1807端⼝：⽊马SpySender开放此端⼝1900端⼝：可被利⽤ddos攻击，⼀般关闭1912端⼝：⾦⼭词霸开放此端⼝1981端⼝：⽊马ShockRave开放此端⼝1999端⼝：⽊马BackDoor,yai开放此端⼝2000端⼝：⽊马GirlFriend 1.3、Millenium 1.0开放此端⼝2001端⼝：⽊马Millenium 1.0、Trojan Cow,⿊洞2001开放此端⼝2003端⼝：GNU 查询2023端⼝：⽊马Pass Ripper开放此端⼝2049端⼝：NFS程序常运⾏于此端⼝2115端⼝：⽊马Bugs开放此端⼝2140端⼝：⽊马Deep Throat 1.0/3.0，The Invasor开放此端⼝2500端⼝：应⽤固定端⼝会话复制的RPC客户2504端⼝：⽹络平衡负荷2565端⼝：⽊马Striker开放此端⼝2583端⼝：⽊马Wincrash 2.0开放此端⼝2801端⼝：⽊马Phineas Phucker开放此端⼝2847端⼝：诺顿反病毒服务开放此端⼝3024端⼝：⽊马WinCrash开放此端⼝3128端⼝：squid http代理服务器开放此端⼝3129端⼝：⽊马Master Paradise开放此端⼝3150端⼝：⽊马The Invasor,deep throat开放此端⼝3210端⼝：⽊马SchoolBus开放此端⼝3306端⼝：MySQL开放此端⼝3333端⼝：⽊马Prosiak开放此端⼝3389端⼝：WINDOWS 2000终端开放此端⼝3456端⼝：inetinfo.exe(互联⽹信息服务)开放端⼝，VAT默认数据3457端⼝：VAT默认控制3527端⼝：Microsoft消息队列服务器3700端⼝：⽊马Portal of Doom开放此端⼝3996端⼝：⽊马RemoteAnything开放此端⼝4000端⼝：腾讯QQ客户端开放此端⼝4060端⼝：⽊马RemoteAnything开放此端⼝4092端⼝：⽊马WinCrash开放此端⼝4133端⼝：NUTS Bootp服务器4134端⼝：NIFTY-Serve HMI协议4141端⼝：Workflow服务器4142端⼝：⽂档服务器4143端⼝：⽂档复制4145端⼝：VVR控制4321端⼝：远程Who Is查询4333端⼝：微型sql服务器4349端⼝：⽂件系统端⼝记录4350端⼝：⽹络设备4351端⼝：PLCY⽹络服务4453端⼝：NSS警报管理4454端⼝：NSS代理管理4455端⼝：PR聊天⽤户4456端⼝：PR聊天服务器4457端⼝：PR注册4480端⼝：Proxy+ HTTP代理端⼝4500端⼝：Lsass开放端⼝，不能关闭4547端⼝：Lanner许可管理4555端⼝：RSIP端⼝4590端⼝：⽊马ICQTrojan开放此端⼝4672端⼝：远程⽂件访问服务器4752端⼝：简单⽹络⾳频服务器4800端⼝：Icona快速消息系统4801端⼝：Icona⽹络聊天4802端⼝：Icona许可系统服务器4848端⼝：App服务器-Admin HTTP4849端⼝：App服务器-Admin HTTPS4950端⼝：⽊马IcqTrojan开放5000端⼝5000端⼝：⽊马blazer5，Sockets de Troie开放5000端⼝，⼀般应关闭5001端⼝：⽊马Sockets de Troie开放5001端⼝5006端⼝：wsm服务器5007端⼝：wsm服务器ssl5022端⼝：mice服务器5050端⼝：多媒体会议控制协议5051端⼝：ITA代理5052端⼝：ITA管理5137端⼝：MyCTS服务器端⼝5150端⼝：Ascend通道管理协议5154端⼝：BZFlag游戏服务器5190端⼝：America-Online(美国在线)5191端⼝：AmericaOnline1(美国在线)5192端⼝：AmericaOnline2(美国在线)5193端⼝：AmericaOnline3(美国在线)5222端⼝：Jabber客户端连接5225端⼝：HP(惠普公司)服务器5226端⼝：HP(惠普公司)5232端⼝：SGI绘图软件端⼝5250端⼝：i⽹关5264端⼝：3Com⽹络端⼝15265端⼝：3Com⽹络端⼝25269端⼝：Jabber服务器连接5306端⼝：Sun MC组5321端⼝：⽊马Sockets de Troie开放5321端⼝5400端⼝：⽊马Blade Runner开放此端⼝5401端⼝：⽊马Blade Runner开放此端⼝5402端⼝：⽊马Blade Runner开放此端⼝5405端⼝：⽹络⽀持5409端⼝：Salient数据服务器5410端⼝：Salient⽤户管理5415端⼝：NS服务器5416端⼝：SNS⽹关5417端⼝：SNS代理5421端⼝：⽹络⽀持25423端⼝：虚拟⽤户5427端⼝：SCO-PEER-TTA(Unix系统)5432端⼝：PostgreSQL数据库5550端⼝：⽊马xtcp开放此端⼝5569端⼝：⽊马Robo-Hack开放此端⼝5599端⼝：公司远程安全安装5600端⼝：公司安全管理5601端⼝：公司安全代理5631端⼝：pcANYWHERE(软件)数据5632端⼝：pcANYWHERE(软件)数据5673端⼝：JACL消息服务器5675端⼝：V5UA应⽤端⼝5676端⼝：RA管理5678端⼝：远程复制代理连接5679端⼝：直接电缆连接5720端⼝：MS-执照5729端⼝：Openmail⽤户代理层5730端⼝：Steltor's⽇历访问5731端⼝：netscape(⽹景)suiteware5732端⼝：netscape(⽹景)suiteware5742端⼝：⽊马WinCrash1.03开放此端⼝5745端⼝：fcopy-服务器5746端⼝：fcopys-服务器5755端⼝：OpenMail(邮件服务器)桌⾯⽹关服务器5757端⼝：OpenMail(邮件服务器)X.500⽬录服务器5766端⼝：OpenMail (邮件服务器)NewMail服务器5767端⼝：OpenMail (邮件服务器)请求代理曾(安全) 5768端⼝：OpenMail(邮件服务器) CMTS服务器5777端⼝：DALI端⼝5800端⼝：虚拟⽹络计算5801端⼝：虚拟⽹络计算5802端⼝：虚拟⽹络计算HTTP访问, d5803端⼝：虚拟⽹络计算HTTP访问, d5900端⼝：虚拟⽹络计算机显⽰05901端⼝：虚拟⽹络计算机显⽰15902端⼝：虚拟⽹络计算机显⽰25903端⼝：虚拟⽹络计算机显⽰36000端⼝：X Window 系统6001端⼝：X Window 服务器6002端⼝：X Window 服务器6003端⼝：X Window 服务器6004端⼝：X Window 服务器6005端⼝：X Window 服务器6006端⼝：X Window 服务器6007端⼝：X Window 服务器6008端⼝：X Window 服务器6009端⼝：X Window 服务器6456端⼝：SKIP证书发送6471端⼝：LVision许可管理器6505端⼝：BoKS管理私⼈端⼝6506端⼝：BoKS管理公共端⼝6507端⼝：BoKS Dir服务器,私⼈端⼝6508端⼝：BoKS Dir服务器,公共端⼝6509端⼝：MGCS-MFP端⼝6510端⼝：MCER端⼝6566端⼝：SANE控制端⼝6580端⼝：Parsec主服务器6581端⼝：Parsec对等⽹络6582端⼝：Parsec游戏服务器6588端⼝：AnalogX HTTP代理端⼝6631端⼝：Mitchell电信主机6667端⼝：Internet多线交谈6668端⼝：Internet多线交谈6670端⼝：⽊马Deep Throat开放此端⼝6671端⼝：⽊马Deep Throat 3.0开放此端⼝6699端⼝：Napster⽂件(MP3)共享服务6701端⼝：KTI/ICAD名称服务器6788端⼝：SMC软件-HTTP6789端⼝：SMC软件-HTTPS6841端⼝：Netmo软件默认开放端⼝6842端⼝：Netmo HTTP服务6883端⼝：⽊马DeltaSource开放此端⼝6939端⼝：⽊马Indoctrination开放此端⼝6969端⼝：⽊马Gatecrasher、Priority开放此端⼝6970端⼝：real⾳频开放此端⼝7000端⼝：⽊马Remote Grab开放此端⼝7002端⼝：使⽤者& 组数据库7003端⼝：⾳量定位数据库7004端⼝：AFS/Kerberos认证服务7005端⼝：⾳量管理服务7006端⼝：错误解释服务7007端⼝：Basic监督进程7008端⼝：服务器-服务器更新程序7009端⼝：远程缓存管理服务7011端⼝：Talon软件发现端⼝7012端⼝：Talon软件引擎7013端⼝：Microtalon发现7014端⼝：Microtalon通信7015端⼝：Talon⽹络服务器7020端⼝：DP服务7021端⼝：DP服务管理7100端⼝：X字型服务7121端⼝：虚拟原型许可证管理7300端⼝：⽊马NetMonitor开放此端⼝7301端⼝：⽊马NetMonitor开放此端⼝7306端⼝：⽊马NetMonitor，NetSpy1.0开放此端⼝7307端⼝：⽊马NetMonitor开放此端⼝7308端⼝：⽊马NetMonitor开放此端⼝7323端⼝：Sygate服务器端7511端⼝：⽊马聪明基因开放此端⼝7588端⼝：Sun许可证管理7597端⼝：⽊马Quaz开放此端⼝7626端⼝：⽊马冰河开放此端⼝7633端⼝：PMDF管理7674端⼝：iMQ SSL通道7675端⼝：iMQ通道7676端⼝：⽊马Giscier开放此端⼝7720端⼝：Med图象⼊⼝7743端⼝：Sakura脚本传递协议7789端⼝：⽊马ICKiller开放此端⼝7797端⼝：Propel连接器端⼝7798端⼝：Propel编码器端⼝8000端⼝：腾讯QQ服务器端开放此端⼝8001端⼝：VCOM通道8007端⼝：Apache(类似iis)jServ协议1.x8008端⼝：HTTP Alternate8009端⼝：Apache(类似iis)JServ协议1.38010端⼝：Wingate代理开放此端⼝8011端⼝：⽊马way2.4开放此端⼝8022端⼝：OA-系统8080端⼝：WWW代理开放此端⼝8081端⼝：ICECap控制台8082端⼝：BlackIce(防⽌⿊客软件)警报发送到此端⼝8118端⼝：Privoxy HTTP代理8121端⼝：Apollo数据端⼝8122端⼝：Apollo软件管理端⼝8181端⼝：Imail8225端⼝：⽊马灰鸽⼦开放此端⼝8311端⼝：⽊马初恋情⼈开放此端⼝8351端⼝：服务器寻找8416端⼝：eSpeech Session协议8417端⼝：eSpeech RTP协议8473端⼝：虚拟点对点8668端⼝：⽹络地址转换8786端⼝：Message客户端8787端⼝：Message服务器8954端⼝：Cumulus管理端⼝9000端⼝：CS监听9001端⼝：ETL服务管理9002端⼝：动态id验证9021端⼝：Pangolin验证9022端⼝：PrivateArk远程代理9023端⼝：安全⽹络登陆-19024端⼝：安全⽹络登陆-29025端⼝：安全⽹络登陆-39026端⼝：安全⽹络登陆-49101端⼝：Bacula控制器9102端⼝：Bacula⽂件后台9103端⼝：Bacula存储邮件后台9111端⼝：DragonIDS控制台9217端⼝：FSC通讯端⼝9281端⼝：软件传送端⼝19282端⼝：软件传送端⼝29346端⼝：C技术监听9400端⼝：⽊马Incommand 1.0开放此端⼝9401端⼝：⽊马Incommand 1.0开放此端⼝9402端⼝：⽊马Incommand 1.0开放此端⼝9594端⼝：信息系统9595端⼝：Ping Discovery服务9800端⼝：WebDav源端⼝9801端⼝：Sakura脚本转移协议-29802端⼝：WebDAV Source TLS/SSL 9872端⼝：⽊马Portal of Doom开放此端⼝9873端⼝：⽊马Portal of Doom开放此端⼝9874端⼝：⽊马Portal of Doom开放此端⼝9875端⼝：⽊马Portal of Doom开放此端⼝9899端⼝：⽊马InIkiller开放此端⼝9909端⼝：域名时间9911端⼝：SYPECom传送协议9989端⼝：⽊马iNi-Killer开放此端⼝9990端⼝：OSM Applet程序服务器9991端⼝：OSM事件服务器10000端⼝：⽹络数据管理协议10001端⼝：SCP构造端⼝10005端⼝：安全远程登陆10008端⼝：Octopus多路器10067端⼝：⽊马iNi-Killer开放此端⼝10113端⼝：NetIQ端点10115端⼝：NetIQ端点10116端⼝：NetIQVoIP鉴定器10167端⼝：⽊马iNi-Killer开放此端⼝11000端⼝：⽊马SennaSpy开放此端⼝11113端⼝：⾦⼭词霸开放此端⼝11233端⼝：⽊马Progenic trojan开放此端⼝12076端⼝：⽊马Telecommando开放此端⼝12223端⼝：⽊马Hack'99 KeyLogger开放此端⼝12345端⼝：⽊马NetBus1.60/1.70、GabanBus开放此端⼝12346端⼝：⽊马NetBus1.60/1.70、GabanBus开放此端⼝12361端⼝：⽊马Whack-a-mole开放此端⼝13223端⼝：PowWow 客户端，是Tribal Voice的聊天程序13224端⼝：PowWow 服务器，是Tribal Voice的聊天程序16959端⼝：⽊马Subseven开放此端⼝16969端⼝：⽊马Priority开放此端⼝17027端⼝：外向连接19191端⼝：⽊马蓝⾊⽕焰开放此端⼝20000端⼝：⽊马Millennium开放此端⼝20001端⼝：⽊马Millennium开放此端⼝20034端⼝：⽊马NetBus Pro开放此端⼝21554端⼝：⽊马GirlFriend开放此端⼝22222端⼝：⽊马Prosiak开放此端⼝23444端⼝：⽊马⽹络公⽜开放此端⼝23456端⼝：⽊马Evil FTP、Ugly FTP开放此端⼝25793端⼝：Vocaltec地址服务器26262端⼝：K3软件-服务器26263端⼝：K3软件客户端26274端⼝：⽊马Delta开放此端⼝27374端⼝：⽊马Subseven 2.1开放此端⼝30100端⼝：⽊马NetSphere开放此端⼝30129端⼝：⽊马Masters Paradise开放此端⼝30303端⼝：⽊马Socket23开放此端⼝30999端⼝：⽊马Kuang开放此端⼝31337端⼝：⽊马BO(Back Orifice)开放此端⼝31338端⼝：⽊马BO(Back Orifice)，DeepBO开放此端⼝31339端⼝：⽊马NetSpy DK开放此端⼝31666端⼝：⽊马BOWhack开放此端⼝31789端⼝：Hack-a-tack32770端⼝：sun solaris RPC服务开放此端⼝33333端⼝：⽊马Prosiak开放此端⼝33434端⼝：路由跟踪34324端⼝：⽊马Tiny Telnet Server、BigGluck、TN开放此端⼝36865端⼝：KastenX软件端⼝38201端⼝：Galaxy7软件数据通道39681端⼝：TurboNote默认端⼝40412端⼝：⽊马The Spy开放此端⼝40421端⼝：⽊马Masters Paradise开放此端⼝40422端⼝：⽊马Masters Paradise开放此端⼝40423端⼝：⽊马Masters Paradise开放此端⼝40426端⼝：⽊马Masters Paradise开放此端⼝40843端⼝：CSCC 防⽕墙43210端⼝：⽊马SchoolBus 1.0/2.0开放此端⼝43190端⼝：IP-PROVISION44321端⼝：PCP服务器(pmcd)44322端⼝：PCP服务器(pmcd)代理44334端⼝：微型个⼈防⽕墙端⼝44442端⼝：ColdFusion软件端⼝44443端⼝：ColdFusion软件端⼝44445端⼝：⽊马Happypig开放此端⼝45576端⼝：E代时光专业代理开放此端⼝47262端⼝：⽊马Delta开放此端⼝47624端⼝：Direct Play服务器47806端⼝：ALC协议48003端⼝：Nimbus⽹关50505端⼝：⽊马Sockets de Troie开放此端⼝50766端⼝：⽊马Fore开放此端⼝53001端⼝：⽊马Remote Windows Shutdown开放此端⼝54320端⼝：⽊马bo2000开放此端⼝54321端⼝：⽊马SchoolBus 1.0/2.0开放此端⼝61466端⼝：⽊马Telecommando开放此端⼝65000端⼝：⽊马Devil 1.03开放此端⼝65301端⼝：PC Anywhere软件开放端⼝。
Micro Focus应用兼容性指南说明书
Micro FocusThe Lawn22-30 Old Bath RoadNewbury, Berkshire RG14 1QNUK© Copyright 2019 Micro Focus or one of its affiliates.MICRO FOCUS, the Micro Focus logo and Visual COBOL and Enterprise Developer aretrademarks or registered trademarks of Micro Focus or one of its affiliates.All other marks are the property of their respective owners.2019-06-19iiContentsApplication Compatibility Guide (4)Compatibility Overview (5)PL/I Application Compatibility (6)COBOL Language Compatibility (7)Third-party Compatibility (8)SOA/IMTK Interface Definition Table (IDT) Compatibility (9)Visual COBOL and Enterprise Developer Windows C Runtime Compatibility (10)Visual COBOL and Enterprise Developer UNIX and Linux C Runtime Compatibility (13)Glossary of Definitions (17)Contents | 3Application Compatibility GuideIf you are planning to upgrade or update to a newer Micro Focus product, then you will be giving somethought to how your existing applications will be affected.Micro Focus supports the forward compatibility of callable artifacts built with one version of a product, andthen deployed and executed on a later version of the product running on the same platform, and in thesame Product Family, unless explicitly specified in the release documentation. The same may also be truefor main executable programs (.exe files), although these files have an extra dependency on the version ofthe C runtime associated with the products used to build and to run the application.This guide aims to demonstrate exactly which products are compatible with each other, and whether or notyou can just deploy your existing applications on a newer product without the need to recompile or relinkthem. This guide covers recommendations for both COBOL and PL/I applications.Use the tables and diagram in the Runtime Compatibility sections of this document to determine exactlywhich products are compatible with each other.Note: Some of the older products in these tables are now out of support. Check the ProductAvailability section on the Micro Focus SupportLine Web site - https:///prodavail.aspx - for more information.4 | Application Compatibility GuideCompatibility OverviewOn a Microsoft Windows platform, when building to a main COBOL executable (.exe), compatibilitydepends on the Microsoft C runtime associated with the products used to build and run the executable. Theexecutable is compatible with any future COBOL products that share a common C runtime with the producton which it was built. See the Visual COBOL and Enterprise Developer Windows C Runtime Compatibilitysections for details on C runtimes used with COBOL products on Windows.However, if the application has a main COBOL executable, and if the product being used for deployment isbased on a C runtime that is later than that in the product used for building the application, thencompatibility cannot be guaranteed. If the behavior of the application changes when you run with the laterversion then Micro Focus strongly recommends that the main executable is relinked with the later product.This will ensure that the COBOL runtime fully handles any runtime error conditions that may occur.Relinking (to the new run time system) enables you to create a new executable capable of running on thelater product, without the need to recompile. T o relink, you must use the object code that was generatedwhen the executable was originally compiled.On UNIX and Linux, COBOL products are built with specific C and C++ compilers, and tested againstspecific versions of the C and C++ runtime. In general, COBOL application artifacts can be executed withlater versions of the C and C++ runtime, unless the C/C++ vendor has specified otherwise; see the VisualCOBOL and Enterprise Developer UNIX and Linux C Runtime Compatibility section for more details. Thecompatibility of glibc versions is similar in nature to a third-party component, such as a RelationalDatabase Management System or Java Application Server, so version checking is advised.Micro Focus does not test all application deployment combinations, but will support valid configurations andrespond to reported incidents if incompatibilities are found, and then make reasonable commercial effortsto provide a solution. However, in some of these circumstances, recompiling with a later version might bethe required action.There are other situations in which recompilation or relinking are the only valid courses of action; forexample, debug and diagnostic output from a mixed deployment environment can only be processed withthe corresponding latest development product that matches the deployment environment. Changes inplatform could also require the application to be modified, recompiled or relinked if external componentsintroduce incompatibilities.When compiling and running managed COBOL applications, applications compiled for .NET managedcode contain references to specific versions of the .NET framework and the COBOL runtime assemblies,but in general, backward compatibility is provided in updated versions. COBOL applications compiled forJVM managed code do not specifically target later Java versions, and in general, will be compatible whenusing a supported Java version.Compatibility Overview | 5PL/I Application CompatibilityPL/I applications currently have more restrictive compatibility support. It is recommended that PL/Iapplications are rebuilt on every release, to ensure application execution behavior is compatible with thePL/I runtime.6 | PL/I Application CompatibilityCOBOL Language CompatibilityThe syntactical and semantic definition of the COBOL language is defined by ANSI, and has beenextended by different vendors such as IBM and Micro Focus. Emulation of a particular standard or vendorversion can by controlled by the use of compiler directives and runtime configuration.The COBOL language definition refers to non-standard usage as having either undefined behavior orundefined results - any application that relies upon this syntax can be subject to changes in behaviorbetween product versions when recompiled.Occasionally, incompatibilities or defects are discovered and corrected. Applications that rely on previouslyincorrect behavior can also be subject to change in later products when recompiled.Upgrading to the latest product on a regular basis will help identify any incremental incompatibilities orreliance on undefined behavior, making your applications more portable and less prone to changesbetween subsequent versions. If there is an extended interval between upgrade and recompilation, then itincreases the risk of application remediation work being required.If you want to take advantage of new product capabilities, such as performance improvements or languageextensions, then recompilation on the latest product will be required.COBOL Language Compatibility | 7Third-party CompatibilityHistorically, Micro Focus has indicated that an operating system or third-party component is supportedonce testing has been completed on that version against a reference COBOL product.The following extended classification of third-party components provides more guidance for customers whoare planning to upgrade to a component before Micro Focus officially classifies it as supported.Note: Planned and Tested status means that Micro Focus will accept incident reports.Micro Focus may also accept incidents for unsupported operating systems if those operating systemsare fully-compatible with a supported operating system. In such circumstances, the incident would betested on the supported operating system, and if the behavior is consistent, it can be investigated. Ifthe problem is believed to be non-Micro Focus related (e.g. an environment issue), you must refer tothe vendor for support.8 | Third-party CompatibilitySOA/IMTK Interface Definition Table (IDT) CompatibilityThe IDT is both forwards- and backwards-compatible: that is, the IDT-related behavior is dependent on theproduct used to build the IDT and the product version used to execute the program that includes the IDT.For example, the latest Visual COBOL product can handle old Net Express IDTs in the same way as NetExpress did. Similarly, an IDT created with Visual COBOL should theoretically be usable by Net Expressand give the same behavior as if it had been created with Net Express. However, to benefit from the latestbehavior that is available, the most recent version of Visual COBOL is always recommended for bothcreation and execution.If you are using a Micro Focus Web or EJB client to communicate with a service running under EnterpriseSever, then the most important thing is to always make sure the client and server are fully in sync (and socontain the same IDT). Problems can occur when customers have updated the client, and then eitherforgotten to re-deploy the service or thought they just didn't need to. Failure to do either of these will causeproblems.32- and 64-bit CompatibilityThe IDT contains no information related to bitism and can generally be used for both 32- and 64-bitdeployment without change.The only exception to this is when the interface COBOL data contains an item that varies in size between32- and 64-bit (such as a pointer or procedure-pointer item), as this may change the alignment of datafields - this is information stored in the IDT, which comes from the COBOL dictionary file. Up to VisualCOBOL/Enterprise Developer 3.0, these pointer types could only be an issue if they existed in the originalinterface of a COBOL service being deployed in Enterprise Server, which admittedly is very rare. However,new support in Visual COBOL/Enterprise Developer 4.0 onwards will itself now use pointers in theinterfaces, and so this may now become more of an issue.SOA/IMTK Interface Definition T able (IDT) Compatibility | 9Visual COBOL and Enterprise Developer Windows C Runtime CompatibilityThe following tables show the version of the C Runtime that is used with each Windows product:10 | Visual COBOL and Enterprise Developer Windows C Runtime CompatibilityRecommendationsThe optimum deployment configuration is to match the build and execution environment versions, as this combination has the most extensive compatibility testing.T o take advantage of the latest deployment product and its associated capabilities and features, such asplatform support, performance, security and product features in a timely manner, you could employ astaged transition of deploying objects built with earlier development products.The compatibility options are described within the following sections, and vary depending on: the productsused, the format of the COBOL application artifacts, and the deployment platform and associated external components.The following table shows the compatibility of each object type, if a staged transition was to be used:If you do not intend to keep the development and deployment product versions aligned, it is recommendedthat you keep the intermediate object code (.obj, .o) from the COBOL compiler and the linker commandline options from the final build prior to deployment. If you subsequently upgrade the deployment product toone that requires the standalone executable to be relinked, then you can rebuild the executable, withouthaving to recompile the application from source with the new COBOL compiler.Compatibility between build and run productsThe following sections show the compatibility between build and run products, on Windows platforms.As previously mentioned, unless explicitly stated in your current release documentation, the callableartifacts of your application will be forward-compatible when running on the same platform, and using alater product, in the same Product Family, to the one in which they were originally built.Visual COBOL and Enterprise Developer Windows C Runtime Compatibility | 11Use the following flow diagram to determine if you need to recompile when building your programs with oneproduct, and then running them with another:Note: If you deploy to an enterprise server, a main executable is not deployed; therefore, you onlyneed to ensure that your callable artifacts are compatible, using the criteria above.12 | Visual COBOL and Enterprise Developer Windows C Runtime CompatibilityVisual COBOL and Enterprise DeveloperUNIX and Linux C Runtime CompatibilityThe following table shows the compatibility of Visual COBOL Development Hub and Enterprise DeveloperUNIX Components products on UNIX/Linux platforms, and their associated C runtime versions.Visual COBOL and Enterprise Developer UNIX and Linux C Runtime Compatibility | 1314 | Visual COBOL and Enterprise Developer UNIX and Linux C Runtime CompatibilityVisual COBOL and Enterprise Developer UNIX and Linux C Runtime Compatibility | 15Note: Enterprise Developer UNIX Components is an integrated component of the EnterpriseDeveloper product, and was first introduced in Enterprise Developer 2.1.16 | Visual COBOL and Enterprise Developer UNIX and Linux C Runtime CompatibilityGlossary of DefinitionsCallable artifacts Binary objects such as .int, .gnt, .lbr, .dll, and .so files that are loaded/called by a standalone executable.Main executable Binary objects that are executable by the system with a main entry point and are run as a separate process, for example .exe on Windows.Object code Binary output from the Compiler, created in platform-defined format (.obj, .o), that can be linked into a standalone executable or callable object, depending on the application. Platform The operating system and third-party components such as RDBMS clients and servers, Java App Servers, JRE and .NET framework, on which the COBOL application is builtand executed.Product Family A set of product releases that have a common base. For example, Visual COBOL for Visual Studio 2012 and Enterprise Developer for Visual Studio 2012.Relinking The action of relinking links a main application executable with the latest run timesystem. Relinking does not require recompilation, but the process does require theoriginal object files that were generated at the point of original compilation. Relink usingthe cbllink command line tool.Glossary of Definitions | 17。
Microfocus Cobol 安装手册
Microfocus Cobol 安装
一．安装环境检查
1.软件安装必要条件
确认小型机上AIX操作系统正确安装
/opt目录下的空闲空间大小至少有1G
拥有root权限的用户
2.软件运行条件
用户将cobol安装成功后，需要导入开发license 和运行license
二．软件安装过程
将软件解压至/opt/microfocus/cobol目录下，如果没有该目录，先创建该目录
安装完毕后，会生成/opt/microfocus/cobol/bin的目录
三．导入许可证
1.运行许可证安装
进入目录/opt/microfocus/mflmf
运行mflmadm（注意：安装前确认你的窗口是80*25字符的大小，否则程序显示的界面会发生问题）
按F3,输入序列号，按TAB键，输入KEY，在敲回车，F3;
敲F7,刷新License
敲ESC,退出
2.开发许可证安装
进入目录/opt/microfocus/cobol/aslmf
运行./apptrack
选择3，输入密码，敲回车
选择6，刷新许可证
选择9，退出
四．验证COBOL安装
编译一个COBOL程序，
compilecob test.COB
如果返回码为0,表示编译成功
验证完毕。
Cobol基本语法总结
コボル基本語法一、COBOL基本語法compla項目使用的Cobol是Micro Focus 公司生产的Cobol,采用在HP-UNIX上运行。
一、cobol的书写格式（每行）1、前6列为序号区(一般不编辑)2、第7列为标示列，仅可以写如下几个标示符。
a. “＊”注释符(注释当前行的代码)b “/“注释符(注释当前行的代码,程序编译时，强制程序清单另起一页,不建议使用)c “－“字符串连接符d “D”DEBUG行标示符(程序为DEBUG模式时，标有该标示符的语句行代码执行，否则和注释行效果一样)3、第8列---11列为A区，包括以下内容。
a 部、节名。
b 层号014、第12列---72列为B区，过程部的程序必须写在B区中。
5、第72以后部分不能编辑。
二、cobol的语法结构(几大部分)1、标示部(IDENTIFICATION DIVISION):提供程序的一般性文档说明,本项目只保留程序名(PROGRAM-ID)一项。
2、环境部(ENVIRONMENT DIVISION): 提供程序外部有关的项目。
a.配置节(CONFIGURATION SECTION)①.指定源计算机(SOURCE-COMPUTE).②.目标计算机(OBJECT-COMPUTE).③.设置debug模式(SOURCE-COMPUTE H9000V WITH DEBUGGING MODE)④. 指定读环境变量设置.SPECIAL-NAMES.ENVIRONMENT-VALUE IS CNS-ENV-PARMENVIRONMENT-NAME IS CNS-ENV-NAME.b. 输入输出节(INPUT-OUTPUT SECTION).文件的物理路径的定义。
方法一：(写死文件路径)SELECT FILE-LOG ASSIGN"/usr3/WSI/commonlog/WSI1101.log"ORGANIZATION IS LINE SEQUENTIAL.方法二:(过程部中动态指定文件)SELECT FILE-LOG ASSIGN TO SELECT-FILEORGANIZATION IS LINE SEQUENTIAL.在数据部定义字符串变量SELECT-FILE,在文件FILE-LOG打开前动态指定文件路径。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Microfocus Cobol 安装
一．安装环境检查
1.软件安装必要条件
确认小型机上AIX操作系统正确安装
/opt目录下的空闲空间大小至少有1G
拥有root权限的用户
2.软件运行条件
用户将cobol安装成功后，需要导入开发license 和运行license
二．软件安装过程
将软件解压至/opt/microfocus/cobol目录下，如果没有该目录，先创建该目录
安装完毕后，会生成/opt/microfocus/cobol/bin的目录
三．导入许可证
1.运行许可证安装
进入目录/opt/microfocus/mflmf
运行mflmadm（注意：安装前确认你的窗口是80*25字符的大小，否则程序显示的界面会发生问题）
按F3,输入序列号，按TAB键，输入KEY，在敲回车，F3;
敲F7,刷新License
敲ESC,退出
2.开发许可证安装
进入目录/opt/microfocus/cobol/aslmf
运行./apptrack
选择3，输入密码，敲回车
选择6，刷新许可证
选择9，退出
四．验证COBOL安装
编译一个COBOL程序，
compilecob test.COB
如果返回码为0,表示编译成功
验证完毕。