Saturday morning I upgraded our programmer test VSE from z/VSE 4.3 to 5.2. The upgrade went well, no problems. This morning I noticed that the TKN value in VSE/POWER job start messages, 1Q47I, has x’40’ as part or all of the value. Examples below. Usually they have a values that have a hex value starting with x’00’, second examples below. Has anyone noticed this on there 5.x systems? If not them it looks like I may have a storage overlay and better open an issue with VSE support. I have the RSL from January 15 applied along with the PSP and corrective service as of June 27. IBMLink doesn’t have any current PTFs for message 1Q47I.
C1 0001 1Q47I C1 CKLPDEVD 36078 FROM NODECHH , TIME= 6:17:15 , TKN=40404040
X1 0001 1Q47I X1 VTSDET 36131 FROM NODEDEVD(R000) , TIME= 6:20:01 , 06:20:01
TKN=404040C7 06:20:01
C1 0001 1Q47I C1 CKLPDEVD 36232 FROM NODECHH , TIME= 6:27:16 , TKN=40404040
N1 0001 1Q47I N1 JJJPMST 36238 FROM NODEDEVD(JJJ) , TIME= 6:27:19 , 06:27:19
TKN=404040D0 06:27:19
F7 0001 1Q47I F7 QAALTAMM 36293 FROM NODEDEVD(R000) , TIME= 6:30:00 ,
TKN=404040D2 06:30:00
X1 0001 1Q47I X1 TPTRNDMJ 30862 FROM NODEDEVD(R000) , TIME= 0:00:06 ,
TKN=00000F15 00:00:06
F8 0001 1Q47I F8 SCICSRPD 30936 FROM NODEDEVD(R000) , TIME= 0:04:26 ,
TKN=00000F19 00:04:26
P1 0001 1Q47I P1 TSAUDDEV 30944 FROM NODEDEVD(R000) , TIME= 0:05:00 ,
TKN=00000F1A 00:05:00
Steve
Steve Mondy
Open Solutions Division
Fiserv
Office: 713-965-8457
Mobile: 281-409-2870
Fax: 281-334-2642
www.fiserv.com
FORTUNE World's Most Admired Companies® 2014 | 2015 | 2016
Facebook: Like Fiserv · Twitter: Follow @Fiserv · LinkedIn: Connect Fiserv
Flipboard: Follow Fiserv Forward · Careers: Join Fiserv
Steve …
On 5.2.0 with RSL 30Jun16 applied. My tokens are leading with x’00’ as expected.
Kevin P Corkery
Independent Consultant
Voorhees, New Jersey
We noticed the same thing here. It is because your first IPL ran an old assembly of the POWER macro.
You can relink it on VSE 5.x but the 4040 will stay until they eventually go to 4041 etc. No harm done.
Louis,
When you say on old assembly of POWER do you mean assembled with POWER macros from an earlier version or release of VSE? I didn’t think POWER would even start with a previous POWER phase?
I checked the listing, it has the correct version,
00290 0000F8 C7D5C3C240404040 184+IPW$POW1 DC C'GNCB V9R2 ' STORAGE DESCRIPTOR @D92CDMW 01-POWER
00291 000108 F9F0F2F0 185+ DC C'9020' VERSION/RELEASE/MOD @D92CDMW 01-POWER
Or are you referring to doing a WARM start of POWER and having POWER do the ‘spool file migration’? That is what I did.
F1 0001 1Q0HI CURRENT LEVEL V9R2 OF VSE/POWER DIFFERENT FROM LEVEL V8R3 OF
QUEUE STARTING WARM 09:04:28
F1-0001 1Q0HD IF SPOOL FILE MIGRATION TO V9R2 IS INTENDED REPLY 'YES', ELSE
'NO' 09:04:28
1 yes 09:04:41
F1 0001 1RB4I PLOAD NETWORK DEFINITION TABLE PNETDEVD LOADED 09:04:41
F1 0001 1Q20I AUTOSTART IN PROGRESS 09:04:42
F1 0001 1R75I BG AUTOSTARTED 09:04:42
F1 0001 1R75I F2 AUTOSTARTED 09:04:42
F1 0001 1R75I F3 AUTOSTARTED 09:04:42
F1 0001 1R75I F4 AUTOSTARTED 09:04:42
F1 0001 1R75I F5 AUTOSTARTED 09:04:42
F1 0001 1R75I F6 AUTOSTARTED 09:04:42
F1 0001 1R75I F7 AUTOSTARTED 09:04:42
F1 0001 1R75I F8 AUTOSTARTED 09:04:42
F1 0001 1R75I F9 AUTOSTARTED 09:04:42
F1 0001 1R75I FA AUTOSTARTED 09:04:42
It doesn’t matter to me what the token values are we won’t be using them. I just want to know this is expected and not the smoke before the fire.
IBM are you out there? I don’t want to open a PMR if this is alright.
Steve
The generated code was upwardly compatible from VSE 4.3.
We were up on VSE 5.1 and could do all of the old POWER commands, just not CTKN=
label POWER ACCOUNT=
label PNODE NODE=name,
AUTH=NET,
LOCAL=YES
Is there a way to reset the value of the token, besides reformatting the power-queues?
From: VSE-L [mailto:vse-l-bounces+geert.dieltiens=inf.van...@lists.lehigh.edu]
On Behalf Of Louis Daugherity
Sent: maandag 18 juli 2016 19:16
To: Steve Mondy <Steve...@opensolutions.com>
Cc: vs...@lists.lehigh.edu
Subject: RE: VSE/POWER Message 1Q47I Job Started TKN Value has X'404040xx' Values
We noticed the same thing here. It is because your first IPL ran an old assembly of the POWER macro.