Please show us the actual contents of one of the actual files that you have shipped to one of your customers (preferably for the data you would have gotten by running your script on Saturday, May 28, 2017 so we can more easily verify which month and quarter values are based on Calendar week dates and which are based on Fiscal week dates). After playing around with your problem a bit, it seems that calendar week values are based on the date values for the Saturday in the week and fiscal week values are based on the date values for the Friday at the end of the same week. Note that the code I'm playing with always produces data for a Saturday (the current date if I run it on Saturday or give it a date to process that is a Saturday OR the immediately prior Saturday if I run it on any other day of the week or give it a date to process that is not a Saturday), so showing me values showing results for a Tuesday just confuses things.
The quoting you have shown us in post #25 for some of these variable can't possibly be correct. For example, the quoting on:
with a zero backslash-escaped and one of two single-quotes backslash-escaped makes absolutely no sense to me as a programmer trying to imagine why any parser would want that input. If you have historical data for the files you have produced for your customers, please show us contents of the files you sent out on 05/28/2017 (presumably the last data you sent out), 01/28/2017, and 12/31/2016.
This User Gave Thanks to Don Cragun For This Post:
Hey Guys.I am a newbie on Bash Shell Scripting and Perl.And I have a question about file parsing.
I have a log file which contains reports about a communication device.I need to take some of the reports from the log file.Its hard to explain the issue.but shortly I can say that, the reports has a... (2 Replies)
Any ideas?
1)loop through text file
2)extract everything between SOL and EOL
3)output files, for example: 123.txt and 124.txt for the file below
So far I have: sed -n "/SOL/,/EOL/{p;/EOL/q;}" file
Here is an example of my text file.
SOL-123.go
something goes here
something goes... (0 Replies)
I was trying to parse the text file, which will looks like this
###XYZABC####
############
int = 4
char = 1
float = 1
.
.
############
like this my text file will contains lots of entries and I need to store these entries in the map eg. map.first = int and map.second = 4 same way I... (5 Replies)
I'm totally stumped with how to handle this huge text file I'm trying to deal with. I really need some help!
Here is what is looks like:
ab1ba67c331a3d731396322fad8dd71a3b627f89359827697645c806091c40b9
0.2
812a3c3684310045f1cb3157bf5eebc4379804e98c82b56f3944564e7bf5dab5
0.6
0.6... (3 Replies)
Hi Friends,
I am back for the second round today - :D
My input text file is this way
Home
friends
friendship meter
Tools
Mirrors
Downloads
My Data
About Us
Help
My own results
BLAT Search Results
ACTIONS QUERY SCORE START END QSIZE IDENTITY CHRO STRAND ... (7 Replies)
I have a text file with records of the form:
A X1 Y1 X2 Y2 X3 Y3
where A is character length 10, Xi is character length 4 and Yi is numeric length 10.
I want to parse the line, and output records like:
A X1 Y1
A X2 Y2
A X3 Y3
etc
Can anyone please give me an idea of how to do this. ... (4 Replies)
Discussion started by: wvdeijk
4 Replies
LEARN ABOUT SUNOS
langinfo.h
langinfo.h(3HEAD) Headers langinfo.h(3HEAD)NAME
langinfo.h, langinfo - language information constants
SYNOPSIS
#include <langinfo.h>
DESCRIPTION
The <langinfo.h> header contains the constants used to identify items of langinfo data (see nl_langinfo(3C)). The type of the constant,
nl_item, is defined as described in <nl_types.h>.
The following constants are defined. The entries under Category indicate in which setlocale(3C) category each item is defined.
Constant Category Meaning
CODESET LC_CTYPE codeset name
D_T_FMT LC_TIME string for formatting date and time
D_FMT LC_TIME date format string
T_FMT LC_TIME time format string
T_FMT_AMPM LC_TIME a.m. or p.m. time format string
AM_STR LC_TIME ante-meridiem affix
PM_STR LC_TIME post-meridiem affix
DAY_1 LC_TIME name of the first day of the week
(for example, Sunday)
DAY_2 LC_TIME name of the second day of the week
(for example, Monday)
DAY_3 LC_TIME name of the third day of the week
(for example, Tuesday)
DAY_4 LC_TIME name of the fourth day of the week
(for example, Wednesday)
DAY_5 LC_TIME name of the fifth day of the week
(for example, Thursday)
DAY_6 LC_TIME name of the sixth day of the week
(for example, Friday)
DAY_7 LC_TIME name of the seventh day of the week
(for example, Saturday)
ABDAY_1 LC_TIME abbreviated name of the first day
of the week
ABDAY_2 LC_TIME abbreviated name of the second day
of the week
ABDAY_3 LC_TIME abbreviated name of the third day
of the week
ABDAY_4 LC_TIME abbreviated name of the fourth day
of the week
ABDAY_5 LC_TIME abbreviated name of the fifth day
of the week
ABDAY_6 LC_TIME abbreviated name of the seventh day
of the week
ABDAY_7 LC_TIME abbreviated name of the seventh day
of the week
MON_1 LC_TIME name of the first month of the year
MON_2 LC_TIME name of the second month
MON_3 LC_TIME name of the third month
MON_4 LC_TIME name of the fourth month
MON_5 LC_TIME name of the fifth month
MON_6 LC_TIME name of the sixth month
MON_7 LC_TIME name of the seventh month
MON_8 LC_TIME name of the eighth month
MON_9 LC_TIME name of the ninth month
MON_10 LC_TIME name of the tenth month
MON_11 LC_TIME name of the eleventh month
MON_12 LC_TIME name of the twelfth month
ABMON_1 LC_TIME abbreviated name of the first month
ABMON_2 LC_TIME abbreviated name of the second
month
ABMON_3 LC_TIME abbreviated name of the third month
ABMON_4 LC_TIME abbreviated name of the fourth
month
ABMON_5 LC_TIME abbreviated name of the fifth month
ABMON_6 LC_TIME abbreviated name of the sixth month
ABMON_7 LC_TIME abbreviated name of the seventh
month
ABMON_8 LC_TIME abbreviated name of the eighth
month
ABMON_9 LC_TIME abbreviated name of the ninth month
ABMON_10 LC_TIME abbreviated name of the tenth month
ABMON_11 LC_TIME abbreviated name of the eleventh
month
ABMON_12 LC_TIME abbreviated name of the twelfth
month
ERA LC_TIME era description segments
ERA_D_FMT LC_TIME era date format string
ERA_D_T_FMT LC_TIME era date and time format string
ERA_T_FMT LC_TIME era time format string
ALT_DIGITS LC_TIME alternative symbols for digits
RADIXCHAR LC_NUMERIC radix character
THOUSEP LC_NUMERIC separator for thousands
YESEXPR LC_MESSAGES affirmative response expression
NOEXPR LC_MESSAGES negative response expression
YESSTR LC_MESSAGES affirmative response for yes/no
queries
NOSTR LC_MESSAGES negative response ro yes/no queries
CRNCYSTR LC_MONETARY local currency symbol, preceded by
'-' if the symbol sould appear
before the value, '+' if the symbol
should appear after the value, or
'.' if the symbol should replace
the radix character
If the locale's values for p_cs_precedes and n_cs_precedes do not match, the value of nl_langinfo(CRNCYSTR) is unspecified.
The <langinfo.h> header declares the following as a function:
char *nl_langinfo(nl_item);
Inclusion of <langinfo.h> header may also make visible all symbols from <nl_types.h>.
USAGE
Wherever possible, users are advised to use functions compatible with those in the ISO C standard to access items of langinfo data. In par-
ticular, the strftime(3C) function should be used to access date and time information defined in category LC_TIME. The localeconv(3C) func-
tion should be used to access information corresponding to RADIXCHAR, THOUSEP, and CRNCYSTR.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO mkmsgs(1), localeconv(3C), nl_langinfo(3C), nl_types.h(3HEAD), setlocale(3C), strftime(3C), attributes(5), standards(5)SunOS 5.10 30 Aug 2002 langinfo.h(3HEAD)