10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi Team
there is a requirement to do validate on Flat files using Shell Scripting.
Suppose we have two flat files ( F1, F2).
Validation
1. Row count between F1 and F2
a) Write it in a file with results of count of each file and differences if any
2. Apply checksum or any... (1 Reply)
Discussion started by: shlearner
1 Replies
2. Shell Programming and Scripting
hi
i have written a script for reading a csv file and creating a flat file, suggest if this script can be optimized
#----------------
FILENAME="$1"
SCRIPT=$(basename $0)
#-----------------------------------------//
function usage
{
echo "\nUSAGE: $THIS_SCRIPT file_to_process\n"... (3 Replies)
Discussion started by: mprakasheee
3 Replies
3. Shell Programming and Scripting
Need to develop a unix shell script for the below requirement and I need your assistance:
1) search for file.log and file.bad file in a directory and read them
2) pull out "Load_Start_Time", "Data_File_Name", "Error_Type" from log file
4) concatinate each row from bad file as... (3 Replies)
Discussion started by: mlpathir
3 Replies
4. Shell Programming and Scripting
i have a flat file with around 700 columns . i want to break it into a flat file with say five columns like
col1,col2,col3,col4
col5,col6,col7,col8
col9...... ,col700
how can i do this (5 Replies)
Discussion started by: r_t_1601
5 Replies
5. Programming
Before i start doing something, I wanted to know whether the approach to compare XML file with UNIX file system structure. I have a pre-configured file(contains a list of paths to executables) and i need to check against the UNIX directory structure. what are the various approches should i use ? I... (6 Replies)
Discussion started by: shafi2all
6 Replies
6. Shell Programming and Scripting
Hi ,
I have a file with contents as below:
Contract Cancellation Report UARCNCL
LOS CODE DATE REAS TYPE AMOUNT AMOUNT LETTER BY
========= ======= ==== ==== ==== ========= ==== ====
8174739 7641509 1S NONE CRCD 30-JUN-2008 NPAR N .00 .00 CCAN
8678696 8091709 1S NONE DDEB 30-JUN-2008... (14 Replies)
Discussion started by: rkumudha
14 Replies
7. Shell Programming and Scripting
Hi
I have a flat file looking this
QWER 2:35 7044 00001 ROUT 1188 EA SS
ASD 2:36 7044 00010 ROUT
BSD 2:37 7044 00011 ROUT
END
QWER 3:35 7044 00011 ROUT 1088 EA SS
ASD 3:36 7044 00010 ROUT
BSD 3:37 7044 00011 ROUT... (9 Replies)
Discussion started by: Krishnaramjis
9 Replies
8. Shell Programming and Scripting
Hi All,
I need a help with a shelll script program.I get a '|' separated file which sometime has a encrypted column.And this encryption sometime breaks the last column data into a new line and this is not picked by the ETL.So when i run a script,it should append back the broken new line data... (11 Replies)
Discussion started by: kumarsaravana_s
11 Replies
9. Shell Programming and Scripting
Hi All,
I get a flat file everyday with some records being invalid.Some records come with less number '|'.I just want to add the missing '|'s ,So the it doesnt give an error insufficient fields while loading...There area total of 32 pipes in each record.
Input:
ASADASD |Y|B|SDFGDSDFD| ... (3 Replies)
Discussion started by: kumarsaravana_s
3 Replies
10. Shell Programming and Scripting
Here is on more go ! Need a shortcut for my problem !
problem is i have a look_update with fixed sequence of column
that is :
MANDT:SERAIL:SERSCHA:SEREX:EQTYP:BSTVP
I will be getting data in a flat file having same number of column but the sequence could be different in each... (5 Replies)
Discussion started by: jambesh
5 Replies
XmResolveAllPartOffsets(3X) XmResolveAllPartOffsets(3X)
NAME
XmResolveAllPartOffsets - A function that allows writing of upward-compatible applications and widgets
SYNOPSIS
#include <Xm/XmP.h>
void XmResolveAllPartOffsets (widget_class, offset, constraint_offset)
WidgetClass widget_class;
XmOffsetPtr * offset;
XmOffsetPtr * constraint_offset;
DESCRIPTION
The use of offset records requires two extra global variables per widget class. The variables consist of pointers to arrays of offsets
into the widget record and constraint record for each part of the widget structure. The XmResolveAllPartOffsets function allocates the off-
set records needed by an application to guarantee upward-compatible access to widget instance and constraint records by applications and
widgets. These offset records are used by the widget to access all of the widget's variables. A widget needs to take the following steps:
Instead of creating a resource list, the widget creates an offset resource list. To help you accomplish this, use the XmPartResource struc-
ture and the XmPartOffset macro. The XmPartResource data structure looks just like a resource list, but instead of having one integer for
its offset, it has two shorts. This is put into the class record as if it were a normal resource list. Instead of using XtOffset for the
offset, the widget uses XmPartOffset.
If the widget is a subclass of the Constraint class and it defines additional constraint resources, create an offset resource list
for the constraint part as well. Instead of using XtOffset for the offset, the widget uses XmConstraintPartOffset in the constraint
resource list.
XmPartResource resources[] = {
{ BarNxyz, BarCXyz, XmRBoolean, sizeof(Boolean),
XmPartOffset(Bar,xyz), XmRImmediate, (XtPointer)False } };
XmPartResource constraints[] = {
{ BarNmaxWidth, BarNMaxWidth,
XmRDimension, sizeof(Dimension),
XmConstraintPartOffset(Bar,max_width),
XmRImmediate, (XtPointer)100 } }; Instead of putting the widget size in the class record, the widget puts the widget part
size in the same field. If the widget is a subclass of the Constraint class, instead of putting the widget constraint record size in
the class record, the widget puts the widget constraint part size in the same field. Instead of putting XtVersion in the class
record, the widget puts XtVersionDontCheck in the class record. Define a variable, of type XmOffsetPtr, to point to the offset
record. If the widget is a subclass of the Constraint class, define a variable of type XmOffsetPtr to point to the constraint offset
record. These can be part of the widget's class record or separate global variables. In class initialization, the widget calls
XmResolveAllPartOffsets, passing it pointers to the class record, the address of the offset record, and the address of the con-
straint offset record. If the widget not is a subclass of the Constraint class, it should pass NULL as the address of the constraint
offset record. This does several things: Adds the superclass (which, by definition, has already been initialized) size field to the
part size field. If the widget is a subclass of the Constraint class, adds the superclass constraint size field to the constraint
size field. Allocates an array based upon the number of superclasses. If the widget is a subclass of the constraint class, allo-
cates an array for the constraint offset record. Fills in the offsets of all the widget parts and constraint parts with the appro-
priate values, determined by examining the size fields of all superclass records. Uses the part offset array to modify the offset
entries in the resource list to be real offsets. The widget defines a constant which will be the index to its part structure in the
offsets array. The value should be 1 greater than the index of the widget's superclass. Constants defined for all Xm widgets can be
found in <XmP.h>.
#define BarIndex (XmBulletinBIndex + 1) Instead of accessing fields directly, the widget must always go through the offset table.
The XmField and XmConstraintField macros help you access these fields. Because the XmPartOffset, XmConstraintPartOffset, XmField,
and XmConstraintField macros concatenate things together, you must ensure that there is no space after the part argument. For exam-
ple, the following macros do not work because of the space after the part (Label) argument:
XmField(w, offset, Label , text, char *) XmPartOffset(Label , text).
Therefore, you must not have any spaces after the part (Label) argument, as illustrated here:
XmField(w, offset, Label, text, char *)
You can define macros for each field to make this easier. Assume an integer field xyz:
#define BarXyz(w) (*(int *)(((char *) w) +
offset[BarIndex] + XtOffset(BarPart,xyz)))
For constraint field max_width:
#define BarMaxWidth(w)
XmConstraintField(w,constraint_offsets,Bar,max_width,Dimension)
The parameters for XmResolveAllPartOffsets are defined below: Specifies the widget class pointer for the created widget Returns the offset
record Returns the constraint offset record
SEE ALSO
XmResolvePartOffsets(3X)
XmResolveAllPartOffsets(3X)