Author: paul.deluca

How Do I Cancel a Print Job in AIX?

To cancel just 1 print job, first identify the job #, by typing the following (We’ll use lp1 as an example):

lpstat -plp1

(make note of the # listed in the “Job” column; we’ll assume it’s “123” for this example)

Type in:

cancel 123

To cancel all print jobs on lp1, type the following:

cancel lp1

To cancel print jobs from the Universe spooler, Find the job # with this command:

usa -j  or usa -p lp1

To cancel one job (i.e. job # 123),  type in

usm -k 123

To delete all jobs in the Universe spooler for lp1:

usm -k -p lp1

How do I schedule a nightly tape backup on AIX?

Traditional tape backups are kicked off by the Eclipse phantom scheduler. The SYS.BACKUP.DVR phantom itself simply executes the /bin/save script, which in turn performs the backup routine and returns a status to Eclipse.

To view/change the nightly backup phantom that runs from within Eclipse:

  • <F2> for System
  • <ALT><A> for Phantom Status
  • <ALT><E> for Schedule
  • Press <Enter> to view all phantoms for all user IDs
  • Select the “System Backup” phantom and press <ALT><E> to Edit
  • When you’ve made the appropriate modifications, press <ESC> to save and exit
For Linux systems, we recommend that you schedule the tape backup and snapshot script simultaneously via crontab, as detailed in this KB article.

How do I restart JBoss on AIX?

Basic Restart Procedure

Log into the server as root and run the following command

/u2/eclipse/modules/bin/services.sh -d jboss

The application server will immediately begin the restart procedure, and it should be back up and running within 2-3 minutes on most servers.

Extended Restart Procedure

If the application server crashes, and attempts to restart it using the basic restart procedure above, or at the direction of Eclipse support, please follow this procedure as root to perform an extended, clean restart of JBoss:

  • Stop the JBoss service:
/u2/eclipse/modules/bin/services.sh -d jboss
  • Kill any errant JBoss processes:
ps -ef|grep jboss|awk '{print $2}'|xargs -i kill -9 {}
  • Kill any errant J2EE (connection pool) phantoms on the database server:
ps -ef|grep SOLAR.J2EE.CONNECTION|awk '{print $2}'|xargs -i kill -4 {}
  • (Optional) Backup logs for diagnosis (releases 8.7.2 and below):
cd /u2/eclipse/modules/jboss/server/eclipse
tar cvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar ./log
  • (Optional) Backup logs for diagnosis (releases 8.7.3 and above):
cd /u2/eclipse/modules/jboss/eclipse
tar cvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar ./log
  • Remove JBoss temporary directories (releases 8.7.2 and below):
rm -rf /u2/eclipse/modules/jboss/server/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/server/eclipse/log
rm -rf /u2/eclipse/modules/jboss/server/eclipse/data
rm -rf /u2/eclipse/modules/jboss/server/eclipse/work
  • Remove JBoss temporary directories (release 8.7.3 and above):
rm -rf /u2/eclipse/modules/jboss/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/eclipse/log
rm -rf /u2/eclipse/modules/jboss/eclipse/data
rm -rf /u2/eclipse/modules/jboss/eclipse/work
  • Remove the CONNECTED.APP.SERVERS control record:
cd /u2/eclipse
/u2/uv/bin/uv
ed control connected.app.servers
fd
y
q
  • Start the JBoss service:
/u2/eclipse/modules/bin/services.sh -e jboss