tmboot命令启动TUXEDO系统的应用，创建必要的IPC资源、启动相关机器的规定的系统和应用服务进程。
tm的主要参数有：
-A 启动所有机器上的管理进程。
-M 启动主控机器上的管理进程。
-i srvid 启动服务id等于srvid的进程。
-g grpname 启动指定的一组服务（含TMS）。
-S 启动所有应用服务。
-s server-name 启动可执行文件名为server-name的服务。
-e 打印本配置所需要的最少的IPC资源。
示例：
tmboot -s s1104Cfm;
s1104Cfm为服务名。
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
以下是BEA的官方参考文档：http://e-docs.bea.com/tuxedo/tux80/atmi/rfcmd31.htm
tmboot
Name
tmboot—Brings up a BEA Tuxedo configuration.
Synopsis
tmboot [-l lmid] [-g grpname] [-i srvid] [-s aout] [-o sequence] [-S] [-A] [-b] [-B lmid] [-T grpname] [-e command] [-w] [-y] [-g] [-n] [-c] [-M] [-d1]
Description
tmboot brings up a BEA Tuxedo application in whole or in part, depending on the options specified. tmboot can be invoked only by the administrator of the bulletin board (as indicated by the UID parameter in the configuration file) or by root. The tmboot command can be invoked only on the machine identified as MASTER in the RESOURCES section of the configuration file, or the backup acting as the MASTER, that is, with the DBBL already running (via the master command in tmadmin(1)). Except, if the -b option is used; in that case, the system can be booted from the backup machine without it having been designated as the MASTER.
With no options, tmboot executes all administrative processes and all servers listed in the SERVERS section of the configuration file named by the TUXCONFIG and TUXOFFSET environment variables. If the MODEL is MP, a DBBL administrative server is started on the machine indicated by the MASTER parameter in the RESOURCES section. An administrative server (BBL) is started on every machine listed in the MACHINES section. For each group in the GROUPS section, TMS servers are started based on the TMSNAME and TMSCOUNT parameters for each entry. All administrative servers are started followed by servers in the SERVERS sections. Any TMS or gateway servers for a group are booted before the first application server in the group is booted. The TUXCONFIG file is propagated to remote machines as necessary. tmboot normally waits for a booted process to complete its initialization (that is, tpsvrinit()) before booting the next process.
Booting a gateway server implies that the gateway advertises its administrative service, and also advertises the application services representing the foreign services based on the CLOPT parameter for the gateway. If the instantiation has the concept of foreign servers, these servers are booted by the gateway at this time.
Booting an LMID is equivalent to booting all groups on that LMID.
Application servers are booted in the order specified by the SEQUENCE parameter, or in the order of server entries in the configuration file (see the description in UBBCONFIG(5)). If two or more servers in the SERVERS section of the configuration file have the same SEQUENCE parameter, then tmboot may boot these servers in parallel and will not continue until they all complete initialization. Each entry in the SERVERS section can have a MIN and MAX parameter. tmboot boots MIN application servers (the default is 1 if MIN is not specified for the server entry) unless the -i option is specified; using the -i option causes individual servers to be booted up to MAX occurrences.
If a server cannot be started, a diagnostic is written on the central event log (and to the standard output, unless -q is specified), and tmboot continues—except that if the failing process is a BBL, servers that depend on that BBL are silently ignored. If the failing process is a DBBL, tmboot ignores the rest of the configuration file. If a server is configured with an alternate LMID and fails to start on its primary machine, tmboot automatically attempts to start the server on the alternate machine and, if successful, sends a message to the DBBL to update the server group section of TUXCONFIG.
For servers in the SERVERS section, only CLOPT, SEQUENCE, SRVGRP, and SRVID are used by tmboot. Collectively, these are known as the server’s boot parameters. Once the server has been booted, it reads the configuration file to find its run-time parameters. (See UBBCONFIG(5) for a description of all parameters.)
All administrative and application servers are booted with APPDIR as their current working directory. The value of APPDIR is specified in the configuration file in the MACHINES section for the machine on which the server is being booted.
The search path for the server executables is APPDIR, followed by TUXDIR/bin, followed by /bin and /usr/bin, followed by any PATH specified in the ENVFILE for the MACHINE. The search path is used only if an absolute pathname is not specified for the server. Values placed in the server’s ENVFILE are not used for the search path.
When a server is booted, the variables TUXDIR, TUXCONFIG, TUXOFFSET, and APPDIR, with values specified in the configuration file for that machine, are placed in the environment. The environment variable LD_LIBRARY_PATH is also placed in the environment of all servers. Its value defaults to $APPDIR:$TUXDIR/lib:/lib:/usr/lib:lib> where
The ULOGPFX for the server is also set up at boot time based on the parameter for the machine in the configuration file. If not specified, it defaults to $APPDIR/ULOG.
All of these operations are performed before the application initialization function, tpsvrinit(), is called.
Many of the command line options of tmboot serve to limit the way in which the system is booted and can be used to boot a partial system. The following options are supported.
-l lmid
For each group whose associated LMID parameter is lmid, all TMS and gateway servers associated with the group are booted and all servers in the SERVERS section associated with those groups are executed.
-g grpname
All TMS and gateway servers for the group whose SRVGRP parameter is grpname are started, followed by all servers in the SERVERS section associated with that group. TMS servers are started based on the TMSNAME and TMSCOUNT parameters for the group entry.
-i srvid
All servers in the SERVERS section whose SRVID parameter is srvid are executed.
-s aout
All servers in the SERVERS section with name aout are executed. This option can also be used to boot TMS and gateway servers; normally this option is used in this way in conjunction with the -g option.
-o sequence
All servers in the SERVERS section with SEQUENCE parameter sequence are executed.
-S
All servers in the SERVERS section are executed.
-A
All administrative servers for machines in the MACHINES section are executed. Use this option to guarantee that the DBBL and all BBL and BRIDGE processes are brought up in the correct order. (See also the description of the -M option.)
-b
Boot the system from the BACKUP machine (without making this machine the MASTER).
-B lmid
A BBL is started on a processor with logical name lmid.
-M
This option starts administrative servers on the master machine. If the MODEL is MP, a DBBL administrative server is started on the machine indicated by the MASTER parameter in the RESOURCES section. A BBL is started on the MASTER machine, and a BRIDGE is started if the LAN option and a NETWORK entry are specified in the configuration file.
-d1
Causes command line options to be printed on the standard output. Useful when preparing to use sdb to debug application services.
-T grpname
All TMS servers for the group whose SRVGRP parameter is grpname are started (based on the TMSNAME and TMSCOUNT parameters associated with the group entry). This option is the same as booting based on the TMS server name (-s option) and the group name (-g).
-e command
Causes command to be executed if any process fails to boot successfully. command can be any program, script, or sequence of commands understood by the command interpreter specified in the SHELL environment variable. This allows an opportunity to bail out of the boot procedure. If command contains white space, the entire string must be enclosed in quotes. This command is executed on the machine on which tmboot is being run, not on the machine on which the server is being booted.
Note: If you choose to do redirection or piping on a Windows 2000 system, you must use one of the following methods:
Do redirection or piping from within a command file or script.
To do redirection from within the queue manager administration program, precede the command with cmd. For example:
cmd /c ipconfig > out.txt
If you choose to create a binary executable, you must allocate a console within the binary executable using the Windows AllocConsole() API function
-w
Informs tmboot to boot another server without waiting for servers to complete initialization. This option should be used with caution. BBLs depend on the presence of a valid DBBL; ordinary servers require a running BBL on the processor on which they are placed. These conditions cannot be guaranteed if servers are not started in a synchronized manner. This option overrides the waiting that is normally done when servers have sequence numbers.
-y
Assumes a yes answer to a prompt that asks if all administrative and server processes should be booted. (The prompt appears only when the command is entered with none of the limiting options.)
-q
Suppresses the printing of the execution sequence on the standard output. It implies -y.
-n
The execution sequence is printed, but not performed.
-c
Minimum IPC resources needed for this configuration are printed.
When the -l, -g, -i, -o, and -s options are used in combination, only servers that satisfy all qualifications specified are booted. The -l, -g, -s, and -T options cause TMS servers to be booted; the -l, -g, and -s options cause gateway servers to be booted; the -l, -g, -i, -o, -s, and -S options apply to application servers. Options that boot application servers fail if a BBL is not available on the machine.The -A, -M, and -B options apply only to administrative processes.
The standard input, standard output, and standard error file descriptors are closed for all booted servers.
Interoperability
tmboot must run on the master node, which in an interoperating application must be the highest release available. tmboot detects and reports configuration file conditions that would lead to the booting of administrative servers such as Workstation listeners on sites that cannot support them.
Portability
tmboot is supported on any platform on which the BEA Tuxedo server environment is supported.
Environment Variables
During the installation process, an administrative password file is created. When necessary, the BEA Tuxedo system searches for this file in the following directories (in the order shown): APPDIR/.adm/tlisten.pw and TUXDIR/udataobj/tlisten.pw. To ensure that your password file will be found, make sure you have set the APPDIR and/or TUXDIR environment variables.
Link-Level Encryption
If the link-level encryption feature is in operation between tmboot and tlisten, link-level encryption will be negotiated and activated first to protect the process through which messages are authenticated.
Diagnostics
If TUXCONFIG is set to a non-existent file, two fatal error messages are displayed:
error processing configuration file
configuration file not found
If tmboot fails to boot a server, it exits with exit code 1 and the user log should be examined for further details. Otherwise tmboot exits with exit code 0.
If tmboot is run on an inactive non-master node, a fatal error message is displayed:
tmboot cannot run on a non-master node.
If tmboot is run on an active node that is not the acting master node, the following fatal error message is displayed:
tmboot cannot run on a non acting-master node in an active application.
If the same IPCKEY is used in more than one TUXCONFIG file, tmboot fails with the following message:
Configuration file parameter has been changed since last tmboot
If there are multiple node names in the MACHINES section in a non-LAN configuration, the following fatal error message is displayed:
Multiple nodes not allowed in MACHINES for non-LAN application.
If tlisten is not running on the MASTER machine in a LAN application, a warning message is printed. In this case, tmadmin(1) cannot run in administrator mode on remote machines; it is limited to read-only operations. This also means that the backup site cannot reboot the master site after failure.
Examples
To start only those servers located on the machines logically named CS0 and CS1, enter the following command:
tmboot -l CS0 -l CS1
To start only those servers named CREDEB that belong to the group called DBG1, enter the following command:
tmboot -g DBG1 -s CREDEB1
To boot a BBL on the machine logically named PE8, as well as all those servers with a location specified as PE8, enter the following command.
tmboot -B PE8 -l PE8
To view minimum IPC resources needed for the configuration, enter the following command.
tmboot -c
The following is an example of the output produced by the -c option:
Ipc sizing (minimum BEA Tuxedo values only) … Fixed Minimums Per Processor SHMMIN: 1 SHMALL: 1 SEMMAP: SEMMNI Variable Minimums Per Processor SEMUME, A SHMMAX SEMMNU, * * Node SEMMNS SEMMSL SEMMSL SEMMNI MSGMNI MSGMAP SHMSEG —— —— —— —— —— —— —— —— sfpup 60 1 60 A + 1 10 20 76K sfsup 63 5 63 A + 1 11 22 76K where 1 = A = 8.
The number of expected application clients per processor should be added to each MSGMNI value. MSGMAP should be twice MSGMNI. SHMMIN should always be set to 1.
The minimum IPC requirements can be compared to the parameters set for your machine. See the system administration documentation for your machine for information about how to change these parameters. If the -y option is used, the display will differ slightly from the previous example.
Notices
The tmboot command ignores the hangup signal (SIGHUP). If a signal is detected during boot, the process continues.
Minimum IPC resources displayed with the -c option apply only to the configuration described in the configuration file specified; IPC resources required for a resource manager or for other BEA Tuxedo configurations are not considered in the calculation.
See Also
tmadmin(1), tmloadcf(1), tmshutdown(1), UBBCONFIG(5)
Administering BEA Tuxedo Applications at Run Time
他是年逾花甲的普通老人，却在一夜之间变成了大众追捧的偶像；他是健康生活的“传教士”，他的走红，引发了健康教育产业化的思考。
今天，卫生部首席健康教育专家洪昭光教授做客“都市聊吧”，用他一贯幽默风趣的语言，向中青年人士发出健康的忠告。 More …
分页查看某个命令的帮助
man ls |more
统计文件字数
wc filename
显示文件内容
cat filename
显示文件内容
pg filename
显示文件内容
more filename
用来监视日志输出
tail -f XXX.log
首先介绍两个方法的语法：
reload 方法，该方法强迫浏览器刷新当前页面。
语法： location.reload([bForceGet]) 参数： bForceGet， 可选参数， 默认为 false，从客户端缓存里取当前页。 true, 则以 GET 方式，从服务端取最新的页面, 相当于客户端点击 F5(“刷新”)
replace 方法，该方法通过指定URL替换当前缓存在历史里（客户端）的项目，因此当使用replace方法之后，你不能通过“前进”和“后退”来访问已经被替换的URL。
语法： location.replace(URL) 参数： URL
在实际应用的时候，重新刷新页面的时候，我们通常使用： location.reload() 或者是 history.go(0) 来做。因为这种做法就像是客户端点F5刷新页面，所以页面的method=”post”的时候，会出现“网页过期”的提示。那是因为Session的安全保护机制。可以想到： 当调用 location.reload() 方法的时候， aspx页面此时在服务端内存里已经存在， 因此必定是 IsPostback 的。如果有这种应用： 我们需要重新加载该页面，也就是说我们期望页面能够在服务端重新被创建， 我们期望是 Not IsPostback 的。这里，location.replace() 就可以完成此任务。被replace的页面每次都在服务端重新生成。你可以这么写： location.replace(location.href)
mandatory
两张数据表：表A和表B；
如果A表是mandatory，那么至少要有一张B表与A表对应；
如果B表是mandatory，那么至少要有一张A表与B表对应；
PD8其实有4个版本，但是都是在安装的时候决定的，主要看你输入的是哪一个序列号，使用的是同一个安装包。它们为：
PowerDesigner PhysicalArchitect 只能做PDM
PowerDesigner DataArchitect 做PDM和CDM
PowerDesigner ObjectArchitect 做PDM, CDM, OOM
PowerDesigner Developer 做PDM和OOM
看来你安装的时候是输入了PowerDesigner Developer的序列号，如果想使用全部功能，请输入PowerDesigner ObjectArchitect的序列号
CDM:
Conceptual Data Model to model the overall logical structure of a database, independent from any software or data storage structure considerations. A valid CDM can be converted to a PDM or an OOM.
PDM:
Physical Data Model (PDM) to model the overall physical structure of a database, taking into account DBMS software or data storage structure considerations. A valid PDM can be converted to a CDM or an OOM.
OOM:
Object Oriented Model (OOM) to model a software system using an object-oriented approach for Java or other object languages. A valid OOM can be converted to a CDM or a PDM.
my process like CYT. ‘For me, generally I create tables first, draw the ERwin file from the database(Reverse Engineer). ‘ then repeat it and edit it.
it is more flexible
参考：
http://www.itpub.net/archiver/tid-2411-page-1.html
http://www.cnblogs.com/xingyukun/archive/2007/08/02/840293.html
IE7在遇到一个新窗口时总是默认在新窗口中打开（就是像IE6一样），但IE7是支持多选项卡的（就是像傲游浏览器一样）。请问如果使其遇到新窗口的链接时默认在新选项卡中打开
解决方案/建议：
请你打开IE7，打开Internet选项，在“常规”选卡中，找到“选项卡”一栏，点设置，在打开的窗口中“从位于以下位置的其他程序打开链接”点“当前窗口中的新选项卡”，点确定，ok；再在上面“遇到弹出窗口时”点“始终在新选项卡中打开弹出窗口”，再点确定，ok。
=============================================
System类的使用
System类提供了一些静态方法来控制系统状态，并作为一个系统资源的仓库。System类提供了四个通用领域的功能性：
（1）标准I/O流；
（2）控制系统属性；
（3）访问当前运行时系统的实用工具和便利方法；
（4）安全性。
标准I/O流
标准输入流、标准输出流和错误流能够作为System类的静态域而可用。
标准输入流的一个示例：
Sysmtem.in的一个示例，从键盘读入字符并输出，遇到exit则退出:
public class Test {
public static void main(String[] args) throws Exception {
String str = “”;
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
while((str = br.readLine()) != null){
if(str.equals(“exit”)){
break;
}
System.out.println(str);
}
}
}
控制系统属性
获取系统属性的一个示例：
public class Test {
public static void main(String[] args) {
System.out.println(System.getProperty(“os.name”));
}
}
输出如下：
Windows XP
实用工具
系统类中包含大量的实用方法，以下是两个示例：
public static long currentTimeMillis()
以毫秒的形式返回当前时间，从格林威治时间1970年1月1日0时0分0秒开始计时。
public static void arraycopy(Object src, int srcPos, Ojbect dst, int dstPos, int count)
复制源数组的内容，源数组从src[srcPos]开始，目标数组则以dst[dstPos]开始。恰好有Count数目的元素被复制。
=============================================
以下是一个运行CMD命令的示例：
public class Test {
public static void main(String[] args) throws Exception {
Runtime.getRuntime().exec(“calc”);
}
}
=============================================
=====================================
java集合框架概述
集合（collection）有时也称为容器（container），是一个对象的持有者，使你能够通过有用的方法对对象进行存储和组织，以便进行更有效的访问。同大多数的编程环境一样，java平台也提供了一套集合框架，主要由一组用来操作对象的接口组成。不同接口描述一组不同数据类型。以下是简化后的集合框架：
Collection
├List
│├LinkedList
│├ArrayList
│└Vector
│ └Stack
└Set
Map
├Hashtable
├HashMap
└WeakHashMap
简单说明：
Collection：集合的根接口。提供诸如add、remove、size、toArray和（重要的）iterator等方法。
List： 接口，继承自 Collection，允许重复，以元素安插的次序来放置元素，不会重新排列。
Set：接口，继承自 Collection，不允许元素的重复，元素的存储没有任何特定的顺序，其使用自己内部的一个排列机制。
Map：接口，是一组成对的键－值对象，即所持有的是key-value pairs。Map中不能有重复的key。拥有自己的内部排列机制。
=====================================
Java IO概述
IO是input、ouput的缩写，指应用程序与外部设备间的输入与输出。与应用程序交互最频繁的外部设备就是磁盘，java中有专门的io包管理磁盘的操作。包java.io通过如下类完成对磁盘操作的管理：File、FileDescriptor 、FileInputStream、FileOutputStream、RamdomAccessFile以及接口 FilenameFilter。 More …