Re: V6R1 Issue

Rob,

Circumstances have conspired to touch on a number of things you've
mentioned.

The box in question is one of about 1800 boxes that belong to a customer of
my customer. Though we provide level one and level two support directly to
the end customer, we are least able to effect what is used where.

The software exists to access a proprietary database and the only money
changing hands is a fee to access the data. Our compensation is strictly
with our customer for suppor. There is no possible way to influence OS
versions. The major of a 2500 total boxes (of all customers) are at V5R2, 3
or 4. There are enough at very early 4 levels to be a PIA.

We've two systems one at V4R5 and one at V5R2. That lets us move (albeit
circuitously) stuff between all customers and ourselves.

We don't need anything in V5R4 or higher so a third box isn't something we
want to go get, especially one that will run V6R1 and it's associated
acquisition costs.

So, the V6R1 person is only culpable for 2 of the 1800 boxes. It is us that,
by default is, bypassing 3 and 4.

This customer asked us last November if the stuff would work on V6 and we
said try it. They ran ANZOBJCVN and it popped back then. I sent them a copy
off our system which seemed observable. They never tried anything until just
last week. So I've been thinking everything was cool until now.

Steve Moland


<rob@xxxxxxxxx> wrote in message
news:OFE54F9DB7.121D9512-ON852575A1.00648C4E-852575A1.0067CF85@xxxxxxxxxxxx

Number 1. On that object, run an ANZOBJCVN on a machine running V5R4 or
V5R3. If it fails that then ask for the resignation of the person who
upgraded their machine to 6.1.

The published rule is that if DSPPGM has anything other than *NO for "All
creation data" then you should be good to go. OPM any value other than
*NONE for "observable information".

Then there's something about if the program was modified using unsupported
interfaces, whatever that means. So I wonder if that negates trying a
DSPPGM to an outfile and querying that for observable information.
Which I am sure that someone running V5R2 or earlier is going to try when
they try bypassing V5R3 and V5R4 and go straight to 6.1 or later.

(see also DSPSRVPGM)


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
"Steve Moland" <steve@xxxxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
04/23/2009 12:26 PM
Subject:
Re: V6R1 Issue
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Thanks for the reply Chuck,

The F/pgm seemed odd to me, so searching only that token on the
web gives only two links [both related to Tivoli agent software but
the same issue] where VEXSIGEX was listed. From that I was able to
see that the error MCH42B5 shares the msg\cause text, so presumably
msgMCH42B5 is what I wanted in the above <edit>.

You are correct, MCH42B5 was the error code and all I could find was the
same Tivoli reference.

In the joblog, was the above message preceded by any other?

Nothing new or different than normal.

Were there any VLIC logs for around\before the date\time [04.22.09

10:59:18.2878] the error was issued?

Do know, haven't asked. They have about 25 boxes and just recently up'd 2
of them the V6R1

Because it's a production box and at level 40 (at the request of the
auditors) everything is screwed down so tight that having the tech person
get anything including a command line takes hours.

They let me use Netmeeting to try to be on the box in question but my
borrowed sign-on didn't have authority to much and the "tell us what
commands you need" bit doesn't work when I'm the prospecting mode.

I just asked about the VLIC log.

I'm not sure I know all the indications which leads one to believe that
stuff is observable, however, I used WRKMOD and checked that each module
had *YES for creation data.

The program is C and other than the target release used, the rest of
create command are the same.

Here is the CRTMOD command used.

Command . . . . . . . . : CRTCMOD MODULE(&L/&N) SRCFILE(&L/&F)
SRCMBR(&N) O
UTPUT(*PRINT) CHECKOUT(*NONE) OPTIMIZE(*NONE) DBGVIEW(*ALL)
DEFINE(BIG_ENDIAN AS
400 EBCDIC ILE '_IS_QSYSINC' IS_IBMAS400) LANGLVL(*EXTENDED)
TGTRLS(V3R2M0)

Here is the CRTPGM command used.

Command . . . . . . . . : CRTPGM PGM(&L/&N) MODULE(&N &L/*N)
BNDDIR(TRSYS61
4T/TRGRCAT QSYS/QSNAPI TRSYS200T/APISECURE TRSYS614T/APIUTIL)
DETAIL(*BASIC) TGT
RLS(V4R2M0)

What type of program is the IMPFRMCD object; what compiler? Can
a DSPPGM output be obtained to review what the OS records about the
object?

Here is the display PGM stuff

Program creation information:
Program creation date/time . . . . . . . . . . : 12/02/04 10:30:50
Type of program . . . . . . . . . . . . . . . : ILE
Program entry procedure module . . . . . . . . : IMPFRMCD
Library . . . . . . . . . . . . . . . . . . : TRSYS200T
Activation group attribute . . . . . . . . . . : *NEW
Shared activation group . . . . . . . . . . . : *NO
User profile . . . . . . . . . . . . . . . . . : *USER
Use adopted authority . . . . . . . . . . . . : *YES
Coded character set identifier . . . . . . . . : 65535
Number of modules . . . . . . . . . . . . . . : 18

Number of service programs . . . . . . . . . . : 5
Number of unresolved references . . . . . . . : 0
Number of copyrights . . . . . . . . . . . . . : 0
All creation data . . . . . . . . . . . . . . : *YES
Observable information compressed . . . . . . : *NO
Run time information compressed . . . . . . . : *NO
Allow update . . . . . . . . . . . . . . . . . : *YES
Allow bound *SRVPGM library name update . . . : *NO
Profiling data . . . . . . . . . . . . . . . . : *NOCOL
Teraspace storage enabled PEP . . . . . . . . : *NO
Teraspace storage enabled modules . . . . . . : *NONE

Here is the module list

Creation Optimization Debug
Opt Module Library Attribute Date Level Data
IMPFRMCD TRSYS200T CLE 01/25/02 *NONE *YES
BIT TRSYS200T CLE 04/03/97 *NONE *YES
GCATALOG TRSYS200T CLE 04/03/97 *NONE *YES
GCDECOMP TRSYS200T CLE 04/03/97 *NONE *YES
GCOMMON TRSYS200T CLE 04/03/97 *NONE *YES
GSHARED TRSYS200T CLE 04/03/97 *NONE *YES
LOADLONG TRSYS200T CLE 04/03/97 *NONE *YES
XSECURE TRSYS200T CLE 04/03/97 *NONE *YES

GCUSTOM TRSYS200T CLE 04/03/97 *NONE *YES
APISYMBL TRSYS200T CLE 04/03/97 *NONE *YES
STRUTIL TRSYS200T CLE 07/17/01 *NONE *YES
XLATE TRSYS200T CLE 04/03/97 *NONE *YES
DOSC400 TRSYS200T CLE 04/03/97 *NONE *YES
TRERROR TRSYS200T CLE 04/03/97 *NONE *YES
ALLOC400 TRSYS200T CLE 04/03/97 *NONE *YES
APIUOBJ TRSYS200T CLE 07/17/01 *NONE *YES
GETINI TRSYS200T CLE 08/30/01 *NONE *YES
TRAUDIT TRSYS200T CLE 05/24/00 *NONE *YES

Here is a typical module.

Module attributes:
Module . . . . . . . . . . . . . . . . . . . . : BIT
Library . . . . . . . . . . . . . . . . . . : TRSYS200T
Source file . . . . . . . . . . . . . . . . . : GSRC
Library . . . . . . . . . . . . . . . . . . : TRSYS200T
Source member . . . . . . . . . . . . . . . . : BIT
Module attribute . . . . . . . . . . . . . . . : CLE
Module creation date/time . . . . . . . . . . : 04/03/97 13:39:01
Source file change date/time . . . . . . . . . : 08/29/96 09:41:20
Coded character set identifier . . . . . . . . : 37
Creation data . . . . . . . . . . . . . . . . : *YES
Sort sequence table . . . . . . . . . . . . . : *HEX
Language identifier . . . . . . . . . . . . . : *JOBRUN
Optimization level . . . . . . . . . . . . . . : *NONE
Maximum optimization level . . . . . . . . . . : *FULL

Debug data . . . . . . . . . . . . . . . . . . : *YES
Profiling data . . . . . . . . . . . . . . . . : *NOCOL
Number of procedures . . . . . . . . . . . . . : 8
Number of procedures block reordered . . . . . : 0
Number of procedures block order measured . . : 0
Enable performance collection . . . . . . . . : *NONE
Teraspace storage enabled . . . . . . . . . . : *NO
Module created on . . . . . . . . . . . . . . : V4R3M0
Module created for . . . . . . . . . . . . . . : V2R3M0
Object control level . . . . . . . . . . . . . :
User modified . . . . . . . . . . . . . . . . : *YES
Licensed program . . . . . . . . . . . . . . . :
PTF number . . . . . . . . . . . . . . . . . . :
APAR ID . . . . . . . . . . . . . . . . . . . :
Licensed Internal Code options . . . . . . . . : *NONE



Steve Moland
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.