10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
We have a mainframe file which is in EBCDIC format.We dont have direct access to mainframe ,client has provided us the mainframe file.The mainframe file is containing pact data(COMP1 ,COMP2 etc) which are unreadble.Can anyone suggest me how to convert this kind of ebcdic file to ascii... (11 Replies)
Discussion started by: swapna_1990
11 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have a input file which is EBCIDIC and it has packed decimals.
Can anyone help me to convert EBCIDIC file to ASCII(Need to convert even Packed decimal values also to normal format).
Thanks
swapna (12 Replies)
Discussion started by: swapna_1990
12 Replies
3. UNIX for Advanced & Expert Users
I have a file in my Unix ( SOLARIS ) with EBCDIC format...I want this file to read in ASCII OR unicode...Is it possible with UNIX to convert this file on ASCII OR UNICODE format from EBCDIC format?
I was searching through web and found only conversion table :(
Request Rejected
Below is... (16 Replies)
Discussion started by: joshilalit2004
16 Replies
4. UNIX for Dummies Questions & Answers
Hi All ,
I have a mainframe file which contains the data in EBCDIC unreadable format.I have downloaded this raw unreadable file from mainframe system to windows in text format then I pushed to Unix system.Now I want to convert this file to ASCII readable format file in unix.Can anyone advise me... (2 Replies)
Discussion started by: STCET22
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
I want to convert ebcdic values to ascii values. Are there anyany specific c++ libraries with g++ compiler, which can do it ?
gcc version 4.1.2 20080704 (Red Hat 4.1.2-54) (0 Replies)
Discussion started by: tostay2003
0 Replies
6. Solaris
Hi All,
I am facing EBCDIC to ASCII Binary conversion on Solaris i-series Unix system.
However this is working fine on Solaris Sparc Unix system.
Input file having EBCDIC format does not work on Solaris i-series Unix system.
Could you please tell me, what will be the root cause for same? (14 Replies)
Discussion started by: amodkavi
14 Replies
7. UNIX for Dummies Questions & Answers
when i try to convert a mainframe EBCDIC file to ASCII ,i dont see correct file this is the source file
... (3 Replies)
Discussion started by: venkatvelpula
3 Replies
8. UNIX for Advanced & Expert Users
Hi all,
At present a file from AS400 system is being FTPed to an AIX system.
Now, a similar file needs to be sent from our Unix box (Solaris)
Is there any tool available which does the conversion in Unix from UTF-8 to EBCDIC?
Any suggestions/ pointers are really appreciated.
Thanks,... (4 Replies)
Discussion started by: sridhar_423
4 Replies
9. Shell Programming and Scripting
Hello,
I need a program for ascii to ebsdic conversion. If anybody can help, it'll be greatly appreciated.
Thanks. (1 Reply)
Discussion started by: er_ashu
1 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I am using HPUX 11. There is a command to convert Unix formatted data to Dos formatted data called 'ux2dos'.
Is there a similar command to convert Unix formatted data to EBCDIC format?
Many thanks
Helen :) (2 Replies)
Discussion started by: Bab00shka
2 Replies
uerf(8) System Manager's Manual uerf(8)
NAME
uerf - Event report formatter
SYNOPSIS
/usr/sbin/uerf [options]
OPTIONS
Selects classes of events. Reports all hardware-detected and software-detected events. Reports any event that occurs during system main-
tenance (for example, if you run a system exerciser). Reports information on system status, autoconfiguration, device status, device
events, time stamps, and system startup and shutdown. Reports events for the specified disk type (for example, rz55) or class (for exam-
ple, rz). If you do not specify the disk type, events for all disk types are reported. Outputs event information from the specified file
instead of the /usr/adm/binary.errlog default event log file. The filename and location of the default event log file is defined by the
*.* entry in the /etc/binlog.conf file. Use the -f option to examine old or backup event log files. You must specify the full path name
for the file. Displays a brief help message. If you specify any other option with the -h option, it is ignored. Reports events from the
specified system. Use the -H option when you want to forward events from multiple remote systems to the local host. Reports mainframe
event types. If you do not specify any parameters, all mainframe events are reported. You can specify the following mainframe event
types: Reports CPU-related events, such as machine checks. Reports memory-related events, such as single-bit corrected read data (CRD) and
double-bit uncorrectable events. Outputs events as they occur in real time before logging the events in the event log file. This option
can be used to monitor events while you are running a disk or tape exerciser. You cannot use the -n option with the -f option. Outputs
events in brief, full, or terse format. The default output is brief. You can specify the following formats: Reports event information in
a short format. Reports all available information for each entry. Reports event information and displays register values, but does not
translate. Reports operating system events such as panics and exceptions and faults. If you do not specify any parameters, all operating
system events are reported. You can specify the following events: Arithmetic exception faults Asynchronous trap exception faults Page
faults Privileged instruction faults Protection faults Page table faults Reserved address faults Reserved operand faults System call excep-
tion faults Segmentation faults Outputs event information in reverse chronological order. Reports events for the specified record code or
codes. You can specify the following record codes: CPU machine checks and exceptions Memory events (soft and hard) Disk events Tape events
Device controller events Adapter events Bus events Stray interrupts Console events Stack dump CAM (SCSI) events ci ppd events scs events
Informational Start up Shutdowns and reboots Panics Diagnostics status Reports events that are included in the specified sequence of num-
bers. You also can specify other options to select the event types in the sequence that you want reported. Produces a summary report of
the selected events. Reports the events that are included in the specified time range. If you do not specify the -t option, the uerf com-
mand processes the event log file from beginning to end. You can specify a starting time and ending time. The default date is the current
date, the default starting time is 00:00:00, and the default ending time is 23:59:59. Use the following syntax to specify the time
sequence: uerf -t s:dd-mmm-yyyy,hh:mm:ss e:dd-mmm-yyyy,hh:mm:ss
The s: parameter specifies the starting time, and the e: parameter specifies the ending time. Reports events for the specified tape
type (for example, tz30) or class (for example, tz). If you do not specify any parameters, events for all tape types are reported.
Reports events for the specified unit number. This option can be used with -D or -T option. Excludes all the selection options
specified in the command line. This option does not affect the -f, -h, -H, -o, -R, and -t options. Produces output in hex format.
DESCRIPTION
The uerf command produces a record of system events. These events include event messages relating to the system hardware and the software
kernel as well as information about system status, startup, and diagnostics.
The event log files are created with 640 mode. The files are owned by root and belong to the system group. If you want to use the uerf
command, you must belong to the system group or have superuser privileges.
RESTRICTIONS
The uerf command uses the uerf.bin, uerf.hlp, and uerf.err data files. The uerf.bin file is the event information data base. The uerf.hlp
file is the help file. The uerf.err file is the event message file. The uerf command expects to find the data files in the /usr/sbin
directory.
By default, the uerf command outputs the contents of the event log file specified by the *.* entry in the /etc/binlog.conf configuration
file. To report on any other event log file or if there is no *.* entry, you must use the uerf command with the -f option.
Do not specify any other option with the -h option.
Some hardware and system events are logged as ASCII informational messages. Use the logger command with the -b option to log informational
messages. Use the uerf command with the -r 250 option to report information messages.
Additional event information also is logged by the syslogd daemon in the file specified by the kern.debug and syslog.debug entries in the
/etc/syslog.conf file. These log files are in ASCII format; you do not have to use the uerf command to read these files.
The uerf command is not compatible with binary event log files produced by ULTRIX or DEC OSF/1 Version 1.0 operating systems.
EXAMPLES
The following example produces a report containing all event events, excluding logged operating system events and operator and maintenance
class events: uerf -O -x -c oper,maint The following example produces an event report from the /usr/adm/binary.errlog.old file: uerf -f
/usr/adm/binary.errlog.old The following examples produce event reports for the specified record codes: uerf -r 100,102
uerf -r 100-109 The following example produces a report of all the events that occurred between 10:47 a.m. on April 13, 1986 and 5:30 p.m.
on April 20, 1986: uerf -t s:13-apr-1986,10:47:00 e:20-apr-1986,17:30:00 The following example produces an event report of the events that
occurred on the current day and year, starting at 1:20 p.m. and ending at the current time: uerf -t s:13:20 The following example produces
a report of all logged events and displays it in reverse chronological order, starting with the current date and time: uerf -R
FILES
default event log file binlogd configuration file uerf event message file uerf help file event information data base file
SEE ALSO
Commands: logger(1), binlogd(8), syslogd(8)
uerf(8)