I´m creating a starter system to be used as a backup when things mess up with my production system. After this clonning process i can log on to the TSO but when i execute the ISPF i receive the following error message:
ISPF ENDED DUE TO ERROR *
after allocated a dsn request (userid.c.clist)
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001
TIME=16.52.07 SEQ=01774 CPU=0000 ASID=0069
PSW AT TIME OF ERROR 078D2000 80AFDD06 ILC 6 INTC 01
NO ACTIVE MODULE FOUND
DATA AT PSW 00AFDD00 - C1E2E7C2 00AFDF30 00AF8620
AR/GR 0: 00000000/00011748 1: 00000000/00010838
2: 00000000/00000007 3: 00000000/00000390
4: 00000000/00016790 5: 00000000/00000098
6: 00000000/00016CA8 7: 00000000/000164C8
8: 00000000/8441A2D8 9: 00000000/00016CA8
A: 00000000/0441B2D7 B: 00000000/00000006
C: 00000000/000106C0 D: 00000000/000106C0
E: 00000000/8441B428 F: 01000002/00AFDD00
END OF SYMPTOM DUMP
I´ve tried to debug the ISPF clist execution but the only thing i get is the Symtom dump error.
Hi, as we have very little information here, if you are willing to accept wild guesses based on assumptions here goes. The PSW where you abend seems to be pointing to the Address Space Extension Block. If this is the case I would take a dump and take a look at where R14 is pointing as R15 seems to have the address of the ASXB so there is a good chance that it has got here using BALR R14,R15. If R14 is in an ISPF module then there is a chance you have an incorrect LPALST/LNKLST concatenation or your logon proc is not correct.
If you issued the command ISPF (and not %ISPF) then allocating a clist dataset should have no affect on the processing.
As mentioned at the beginning this is pure guesswork based on (very) limited information and if it bears no resemblance to reality feel free to nominate it for a Booker Prize